Re: Very slow processing on SSAS2005 Std (Core Duo, MSSQL on same box, different disks for DB and AS)...

Thanks Jeje - I shall investigate (admittedly, this is a very simple
project, I'm just playing with SSAS on my home PC!).

"Jeje" <willgart@xxxxxxxxxxx> wrote in message
news:583AE4F0-0CB3-4EB6-BC98-7D4FE2261B63@xxxxxxxxxxxxxxxx
having both SQL and SSAS on the same server required that the user to be
authenticated against your AD.
so the problem come from some mistakes in the network config and the
result is a slow login process.
in fact you have found a possible issue on your server.

the service account is local on the server and don't required any network
access to validate the account. its why its fast.

later in your project you can suffer issues or slow access to the cubes if
your login still slow.
so try to solve it to insure your performance.

"Will Alber" <junk@xxxxxxxxxxxxxxx> wrote in message
news:ud3vF0jxHHA.276@xxxxxxxxxxxxxxxxxxxxxxx
Thanks Jeje. Both servers (MSSQL / AS) are on the same box - whether my
router is coming into play or not is another matter.

Service account => blindingly fast. :)

"Jeje" <willgart@xxxxxxxxxxx> wrote in message
news:75EB1331-9224-4757-BE32-8C77BF290265@xxxxxxxxxxxxxxxx
I think you have some network issues like DNS bad configuration.
so authenticating the user is slow due to a slow name resolution.

verify that the station and the server DNS server is the DC IP address.
(the first DNS Server should be the DC server)

but you have a good solution by switching to the service account.


"Will Alber" <junk@xxxxxxxxxxxxxxx> wrote in message
news:O5FDgcexHHA.3720@xxxxxxxxxxxxxxxxxxxxxxx
D'oh - that's the last time I provide credentials for impersonation.

Setting the impersonation to 'Use Service Account' sorted it,
bizarrely. I was using the credentials for my PC, apparently this lead
to serious performance issues, I expect that I was hitting a network
timeout or similar each time authentication was required. Processing
dropped from ~2 mins to ~1 sec after using service account. :)

"Will Alber" <junk@xxxxxxxxxxxxxxx> wrote in message
news:eK2eCXexHHA.600@xxxxxxxxxxxxxxxxxxxxxxx
Hi All,

I have a very simple cube (my bank account transactions), with around
500 fact table rows, a handful of very small dimensions, including a
date dimension built by SSAS.

When I process this cube, it takes 2 mins+, the majority of the time
being spent processing the dimensions.

I've profiled MSSQL (where the 'subject matter' DB is), and the sum
total of duration for queries used to build the cube amounts to around
a second.

I'm struggling to see why SSAS would be having a hard time building
this cube - any thoughts?

Many thanks,

Will Alber.







.

Relevant Pages

  • Re: Very slow processing on SSAS2005 Std (Core Duo, MSSQL on same box, different disks for DB and AS
    ... so authenticating the user is slow due to a slow name resolution. ... verify that the station and the server DNS server is the DC IP address. ... but you have a good solution by switching to the service account. ... I have a very simple cube, ...
    (microsoft.public.sqlserver.olap)
  • Re: Very slow processing on SSAS2005 Std (Core Duo, MSSQL on same box, different disks for DB and AS
    ... having both SQL and SSAS on the same server required that the user to be authenticated against your AD. ... the service account is local on the server and don't required any network access to validate the account. ... so authenticating the user is slow due to a slow name resolution. ... I have a very simple cube, with around 500 fact table rows, a handful of very small dimensions, including a date dimension built by SSAS. ...
    (microsoft.public.sqlserver.olap)
  • Re: Running Analysis Server 2000 on seperate box
    ... changing the service account sorted things. ... with 2GB ram on Windows Server 2003. ... The server has both the database and Analysis Services ... >to use Local System which is fine for local databases, ...
    (microsoft.public.sqlserver.olap)
  • Re: SPN for SSL over common name
    ... you can't register those SPNs under the SQL Server's ... service account is the MSSQL SPN. ... That SPN should be registered under ... Lastly, since the SQL Server is not being used for delegation anywhere, ...
    (microsoft.public.inetserver.iis.security)
  • Re: In SSP Admin page Search Setting link fails with access denied
    ... First I modified the permissions of the SSP service account as you said. ... administratie and service accounts (Office SharePoint Server): ... How to change the passwords for service accounts in SharePoint Server ...
    (microsoft.public.sharepoint.portalserver)
Loading