Re: Running Analysis Server 2000 on seperate box
- From: Mark <one@xxxxxxx>
- Date: Wed, 27 Jul 2005 19:53:35 +0100
Thanks for that, changing the service account sorted things.
The reason for the test is on going issue.
I have a client with SQL Server 2000 SP3a on a dual Xeon 2.4Ghz box
with 2GB ram on Windows Server 2003. This is hosting a Datawarehouse
solution. The client is increasing their requirement for OLAP cubes
and reporting. The server has both the database and Analysis Services
installed. There are currently 7 cubes on the AS server. The Server
memory is probably operating at the limit with the Page File reaching
3.5GB. I have experienced an issue when building these
cubes/dimensions where the query reads the rows, produces a completed
processing time but then locks up just before the end, and seemingly
the only solution is to stop the olap service. Restarting results in
the following error:
Error 1053: The service did not respond to the start or control
request in a timely fashion.
The service however continues to start, consuming memory, and will
eventually show a started status.
I have set up a test with Analysis Services on it's own server to see
if this is a better solution. I have a copy of the database feeding
the olap cubes to see if the system behaves in the same way. The
server I have is a PIII 733Mhz with 512MB ram and 2x20GB drives.
So far AS has locked up in the same way as above when processing the
last of 12 dimensions. Stopping the olap service and restarting
produces the same error as above. When the service has restarted it
is consuming 65mb of physical ram and 1.1GB of virtual memory, when it
locks it has 117mb of ram and 1.29GB of virtual memory.
Is the lock up issue due to reaching a resource limit?
The cubes are not huge the biggest being 43mb and the smallest 11mb.
I can set up queries to build cub files through msquery with the same
data without a problem.
Any suggestions appreciated, am I experiencing an error condition that
can be rectified or is it a case of building a server with a
particular configuration to cope.
On Wed, 27 Jul 2005 09:03:34 -0700, "Dave Wickert [MSFT]"
<dwickert@xxxxxxxxxxxxxxxxxxxx> wrote:
>The service account that the MSSQLServerOLAPService (msmdsrv.exe) is running
>under must be domain account with access to the data source. The default is
>to use Local System which is fine for local databases, but the Local System
>account does not have any network access. Use the Services applet to change
>the service account to a domain account that has netowrk access to the data
>soruce.
>--
>Dave Wickert [MSFT]
>dwickert@xxxxxxxxxxxxxxxxxxxx
>Program Manager
>BI SystemsTeam
>SQL BI Product Unit (Analysis Services)
.
- Follow-Ups:
- References:
- Running Analysis Server 2000 on seperate box
- From: Mark
- Re: Running Analysis Server 2000 on seperate box
- From: Dave Wickert [MSFT]
- Running Analysis Server 2000 on seperate box
- Prev by Date: Re: Analysis Services Command line
- Next by Date: Re: Drillthrough problems
- Previous by thread: Re: Running Analysis Server 2000 on seperate box
- Next by thread: Re: Running Analysis Server 2000 on seperate box
- Index(es):
Relevant Pages
|
