![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
We are using SSAS 2005. However my Chief Operating Office (big Cheese) had problems at his last company with Analysis services only being able to have a maximum of 32 Concurrent Session. So my questions are: 1. Was this a known problem pre SSAS 2005 (or is he talking ....) 2. If it was an issue then has it been resolved in SSAS 2005 Standard Edition? Sorry I can not provide more information. Regards Mike Kimber |
#3
| |||
| |||
|
|
No there was no such limit for AS2k, however... ....because AS2k made heavy use of the client side pivot table services, it was not really well suited to web based reporting. It was possible that each separate connection would cache its own copy of all the dimension, limiting the scaleability of the solution. Depending on the size of the database in question, with a web based presentation layer, it is possible that an AS2k solution would not have scaled above 32 concurrent connections. AS2k5 has a completely different architecture, only sending the result sets back to the client and using a more centralized query processing model. So particularly if you are considering a web based presentation layer it should scale significantly better. Using thick clients both AS2k and AS2k5 would scale to significantly more than 32 concurrent sessions. -- Regards Darren Gosbell - SQL Server MVP Blog: http://www.geekswithblogs.net/darrengosbell In article <C0AA9A67-055F-418B-927D-14854FF549E6 (AT) microsoft (DOT) com>, mikekimber1 (AT) discussions (DOT) microsoft.com says... We are using SSAS 2005. However my Chief Operating Office (big Cheese) had problems at his last company with Analysis services only being able to have a maximum of 32 Concurrent Session. So my questions are: 1. Was this a known problem pre SSAS 2005 (or is he talking ....) 2. If it was an issue then has it been resolved in SSAS 2005 Standard Edition? Sorry I can not provide more information. Regards Mike Kimber |
#4
| |||
| |||
|
|
Darren, Thank you very much, its exactly what I wanted to here! Regards Mike Kimber "Darren Gosbell" wrote: No there was no such limit for AS2k, however... ....because AS2k made heavy use of the client side pivot table services, it was not really well suited to web based reporting. It was possible that each separate connection would cache its own copy of all the dimension, limiting the scaleability of the solution. Depending on the size of the database in question, with a web based presentation layer, it is possible that an AS2k solution would not have scaled above 32 concurrent connections. AS2k5 has a completely different architecture, only sending the result sets back to the client and using a more centralized query processing model. So particularly if you are considering a web based presentation layer it should scale significantly better. Using thick clients both AS2k and AS2k5 would scale to significantly more than 32 concurrent sessions. -- Regards Darren Gosbell - SQL Server MVP Blog: http://www.geekswithblogs.net/darrengosbell In article <C0AA9A67-055F-418B-927D-14854FF549E6 (AT) microsoft (DOT) com>, mikekimber1 (AT) discussions (DOT) microsoft.com says... We are using SSAS 2005. However my Chief Operating Office (big Cheese) had problems at his last company with Analysis services only being able to have a maximum of 32 Concurrent Session. So my questions are: 1. Was this a known problem pre SSAS 2005 (or is he talking ....) 2. If it was an issue then has it been resolved in SSAS 2005 Standard Edition? Sorry I can not provide more information. Regards Mike Kimber |
#5
| |||
| |||
|
|
Darren, Thank you very much, its exactly what I wanted to here! Regards Mike Kimber "Darren Gosbell" wrote: No there was no such limit for AS2k, however... ....because AS2k made heavy use of the client side pivot table services, it was not really well suited to web based reporting. It was possible that each separate connection would cache its own copy of all the dimension, limiting the scaleability of the solution. Depending on the size of the database in question, with a web based presentation layer, it is possible that an AS2k solution would not have scaled above 32 concurrent connections. AS2k5 has a completely different architecture, only sending the result sets back to the client and using a more centralized query processing model. So particularly if you are considering a web based presentation layer it should scale significantly better. Using thick clients both AS2k and AS2k5 would scale to significantly more than 32 concurrent sessions. -- Regards Darren Gosbell - SQL Server MVP Blog: http://www.geekswithblogs.net/darrengosbell In article <C0AA9A67-055F-418B-927D-14854FF549E6 (AT) microsoft (DOT) com>, mikekimber1 (AT) discussions (DOT) microsoft.com says... We are using SSAS 2005. However my Chief Operating Office (big Cheese) had problems at his last company with Analysis services only being able to have a maximum of 32 Concurrent Session. So my questions are: 1. Was this a known problem pre SSAS 2005 (or is he talking ....) 2. If it was an issue then has it been resolved in SSAS 2005 Standard Edition? Sorry I can not provide more information. Regards Mike Kimber |
#6
| |||
| |||
|
|
Clarification: this 32 concurrent session limit was there in the XMLA SDK and in the ADOMD.NET->AS2000 scenarios. In the XMLA SDK it is configurable in the datasources.xml file. For an ADOMD.NET hotfix we also lifted the limitation -- but as Darren mentions below, it is expected to have scalability issues in some situations due to the thick client design... Thanks, Akshai -- Try out the MSDN Forums for Analysis Services at: http://forums.microsoft.com/MSDN/Sho...ID=83&SiteID=1 This posting is provided "AS IS" with no warranties, and confers no rights Please do not send email directly to this alias. This alias is for newsgroup purposes only. "mikekimber1" <mikekimber1 (AT) discussions (DOT) microsoft.com> wrote in message news:6CAEFAA5-2ABB-4196-A9DF-1BC070BBE25C (AT) microsoft (DOT) com... Darren, Thank you very much, its exactly what I wanted to here! Regards Mike Kimber "Darren Gosbell" wrote: No there was no such limit for AS2k, however... ....because AS2k made heavy use of the client side pivot table services, it was not really well suited to web based reporting. It was possible that each separate connection would cache its own copy of all the dimension, limiting the scaleability of the solution. Depending on the size of the database in question, with a web based presentation layer, it is possible that an AS2k solution would not have scaled above 32 concurrent connections. AS2k5 has a completely different architecture, only sending the result sets back to the client and using a more centralized query processing model. So particularly if you are considering a web based presentation layer it should scale significantly better. Using thick clients both AS2k and AS2k5 would scale to significantly more than 32 concurrent sessions. -- Regards Darren Gosbell - SQL Server MVP Blog: http://www.geekswithblogs.net/darrengosbell In article <C0AA9A67-055F-418B-927D-14854FF549E6 (AT) microsoft (DOT) com>, mikekimber1 (AT) discussions (DOT) microsoft.com says... We are using SSAS 2005. However my Chief Operating Office (big Cheese) had problems at his last company with Analysis services only being able to have a maximum of 32 Concurrent Session. So my questions are: 1. Was this a known problem pre SSAS 2005 (or is he talking ....) 2. If it was an issue then has it been resolved in SSAS 2005 Standard Edition? Sorry I can not provide more information. Regards Mike Kimber |
![]() |
| Thread Tools | |
| Display Modes | |
| |