dbTalk Databases Forums  

Analysis Services 32 Conurrent Session Limit?

microsoft.public.sqlserver.olap microsoft.public.sqlserver.olap


Discuss Analysis Services 32 Conurrent Session Limit? in the microsoft.public.sqlserver.olap forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
mikekimber1
 
Posts: n/a

Default Analysis Services 32 Conurrent Session Limit? - 09-14-2006 , 04:13 AM






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


Reply With Quote
  #2  
Old   
Darren Gosbell
 
Posts: n/a

Default Re: Analysis Services 32 Conurrent Session Limit? - 09-14-2006 , 08:49 AM






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...
Quote:
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



Reply With Quote
  #3  
Old   
mikekimber1
 
Posts: n/a

Default Re: Analysis Services 32 Conurrent Session Limit? - 09-14-2006 , 09:28 AM



Darren,

Thank you very much, its exactly what I wanted to here!

Regards Mike Kimber

"Darren Gosbell" wrote:

Quote:
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




Reply With Quote
  #4  
Old   
dbahooker@hotmail.com
 
Posts: n/a

Default Re: Analysis Services 32 Conurrent Session Limit? - 09-14-2006 , 06:43 PM



yeah i agree; there is no such limit in SSAS 2000.

2005 is a _LOT_ more scalable; I would really really reccomend getting
some top of the line hardware though


mikekimber1 wrote:
Quote:
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





Reply With Quote
  #5  
Old   
Akshai Mirchandani [MS]
 
Posts: n/a

Default Re: Analysis Services 32 Conurrent Session Limit? - 09-14-2006 , 07:01 PM



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

Quote:
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






Reply With Quote
  #6  
Old   
mikekimber1
 
Posts: n/a

Default Re: Analysis Services 32 Conurrent Session Limit? - 09-15-2006 , 01:24 AM



Akshai,

Again thankyou for the quick response. We are using SSAS 2005 only, so
provdinig this is resolved in this version which it appears it is we are
happy.

Regards Mike Kimber

"Akshai Mirchandani [MS]" wrote:

Quote:
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







Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.