Re: Analysis Server 2000 Tuning

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

The AS Performance and Operations Guides
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/ansvcspg.mspx
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/anservog.mspx
have several excellent best practices which you might find interesting.
--
Dave Wickert [MSFT]
dwickert@xxxxxxxxxxxxxxxxxxxx
Program Manager
BI Systems Team
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.


"Tim Chapla" <tchapla@xxxxxxxxxxxxxxxxxxx> wrote in message
news:uEdTC%23cxFHA.612@xxxxxxxxxxxxxxxxxxxxxxx
> Web Machine
> Microsoft Windows 2000 Advanced Server SP4
> Dual proc 550 mhz
> 1 gig ram
> .NET Framework 1.1.4332
>
> Analysis Server/SQL Server Machine
> Microsoft Windows 2003 (no service pack due to some incompatibilities
> with other software)
> Quad Proc 2ghz
> 4 gig ram
> SQL Server 2000 SP4
> Analysis Services SP4
>
> We are running a .NET application that connects to an Analysis Services
> Database using ADOMD.NET. The reports we generate require 10 mdx queries
> per report. We tried using a multidimensional ADOMD.NET Cellset to bring
> back multiple dimensions in a single query, and that proved to be
> extremely
> heavy. I have tried ADODB recordsets, ADOMD cellsets, and now we are
> using
> ADOMD.NET cellsets to make 10 trips, ByRef AdomdConnection object, to the
> Analysis Server. When I record a test in Application Center to load test
> this app, it will spike around 400 RPS in the first 10 seconds and then go
> flat. I have tried several different iterations of Connection string
> parameters,
> Restricted Client=2; -- (is not recognized)
> Client Cache Size=100;
> Auto Synch Period=100000;
> Execution Location=3;
> Large Level Threshold=100;
> Connect Timeout=120;
>
> The following link very closely describes our current scenario:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;903005
>
> But again, we cannot get Restricted Client=2 to be recognized in the
> connection string.
>
> I cannot get this app to perform. We have seen several errors, mostly
> http
> timeouts from the web box, or service overloaded errors.
>
> thank you for any info,
> tim
>
>


.

Relevant Pages