Re: OLAP OLEDB Client Slow to Connect

What is the time needed to lookup your NT credentials on the NT domain?
Try this experiment. Create a virtual directory (configured to use NTLM) on
the web server. Then in the folder create a simple readme.htm file which
just says hello. Then put an ACL on it so that only your NT account can read
it. Look at it from a remote client machine in an account with no access
(confirm that you get an error); look at it from the same client machine in
an account with access (confirm that you get the "hello" message). Now.. how
long did it take for the rendering of the Hello html page? That will tell
you how long it took to get your NT credentials.

Analysis Services has to do the same thing. It has to impersonate you on a
thread. That impersonation needs to do a lookup of your NT credentials. One
of the delays which you are mentioning could be from the validation of those
credentials :-(

Just a thought. From your description that is the first place I'd look.
--
Dave Wickert [MSFT]
dwickert@xxxxxxxxxxxxxxxxxxxx
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Mark" <Mark@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D977ABEE-AEBE-4448-B69B-3C941FEFE92F@xxxxxxxxxxxxxxxx
> Hello,
>
> I have been seeing very slow performance in connecting to a OLAP server
from
> a client on a different machine. Originally I was connecting from a
ASP.NET
> page, but I have it localized to a simple test app which creates a OLEDB
> connection using MSOLAP.2 provider to a remote database. If I simply
create
> the connection, open it and close it, it takes 15 seconds. If I put this
is
> a loop, each interation takes 15 seconds so it is not a .Net Jit delay.
>
> In my normal application after the 15 second connection delay I can issue
a
> MDX query and the results are returned in 10's of ms. So the connection
is
> being established but it takes a very long time.
>
> If I use the same application on the OLAP server and connect locally, it
> connects in ms. Everything is running SP3a. My query string has just the
> provider specification and the Data Source defined. No other options set.
>
> This connection delay is making my application unusable, does anyone know
> what is going on? Or how I could futher diagnose it?
>
> Other details. AS 2000, SP3a. All machines running Windows 2003, no SP.
> Client machine just has AS Client components. Reproducible on two
different
> client machines.
>
> Help?
>
> Thanks in advance,
> Mark
>
>


.

Relevant Pages

  • Re: Do Cached Credentials Ever Get Updated?
    ... different client machine? ... If you wanted to update the caches credentials on the computer you will ... They are not actually logging on locally. ... Forever after, they logon locally with NO network connection whatsoever, ...
    (microsoft.public.windows.server.active_directory)
  • Re: Terminal Services Security Issue with Cached Credentials
    ... on a server and then tried connecting to it using cached credentials. ... What version of the Terminal Services client are you using? ... "Always prompt client for password upon connection" ...
    (microsoft.public.windows.server.security)
  • Re: Connecting a remote workstation to a domain
    ... Merv Porter [SBS-MVP] ... VPN for "All Users" to the SBS server (and using her domain credentials). ... connection directly to the SBS network, ...
    (microsoft.public.windows.server.sbs)
  • Re: Connecting a remote workstation to a domain
    ... VPN for "All Users" to the SBS server (and using her domain credentials). ... created the VPN connection and tested with the same results from a remote ... Even setting up a low end workstation ...
    (microsoft.public.windows.server.sbs)
  • Re: Windows Explorer changes user account during connection to share folder
    ... computer through net by Explorer then Explorer kinds of remember the ... successful credentials all times so that if I closes Explorer but later I ... start Explorer try to open connection to same computer it uses same user ... Credential storage is empty since I didn't ask Windows ...
    (microsoft.public.windows.server.security)