|
Home > Archive > MS SQL Server OLAP > January 2006 > Client connect SQL Server 2005 AS
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Client connect SQL Server 2005 AS
|
|
| Clarkie 2006-01-26, 8:23 pm |
| Hello!
I am trying to deploy an OLAP client written in .NET.
My test machine is freshly installed Win XP SP2. The only things installed
at this stage are:
- PTSclient.exe (SQL Server SP 4)
- My application
- Windows Installer 3.1
- MSXML6
(Pretty clean, huh?)
The client app is working fine. Everything runs smoothly when testing
against several different SQL Server AS 2000-machines. The driver used is of
course Analysis Services 8.0
To be able to connect to SQL Server 2005 I then install
Microsoft SQL Server 2005 Analysis Services 9.0 OLE DB Provider
Problem : Now my client app is extremly slow, what previously took a few
seconds could take almost a minute. Note: I am still connecting to AS 2000,
with the 8.0 driver! Some nasty things are happening down there in driver
hell. My performance profiler tells me it's all about the connection. The
code line opening the connection is executing like a turtle on valium. There
is almost no processor usage and memory is plenty.
Now I reckon Microsoft let MSAS 2005 out of the box a bit to early, but
please prove me wrong before I go nuts. Again.
| |
| Akshai Mirchandani [MS] 2006-01-26, 8:23 pm |
| If you know you are connecting to AS 2000, you should be able to just
specify MSOLAP.2 on the connection string... This should make the connection
faster.
Delegating through MSOLAP.3 (the AS 2005 provider) means that the provider
will first attempt to connect to AS 2005 and then to AS 2000 and so you see
a delay.
As far as I recall, another option would be to specify ConnectTo=8.0; on the
connection string -- I believe this should make it go straight to AS 2000...
Thanks,
Akshai
--
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.
"Clarkie" < clarkbones@removeroc
ketmailremove.com> wrote in message
news:%23IpTSVtIGHA.1848@TK2MSFTNGP12.phx.gbl...
> Hello!
>
> I am trying to deploy an OLAP client written in .NET.
>
> My test machine is freshly installed Win XP SP2. The only things installed
> at this stage are:
> - PTSclient.exe (SQL Server SP 4)
> - My application
> - Windows Installer 3.1
> - MSXML6
>
> (Pretty clean, huh?)
>
> The client app is working fine. Everything runs smoothly when testing
> against several different SQL Server AS 2000-machines. The driver used is
> of course Analysis Services 8.0
>
> To be able to connect to SQL Server 2005 I then install
> Microsoft SQL Server 2005 Analysis Services 9.0 OLE DB Provider
>
> Problem : Now my client app is extremly slow, what previously took a few
> seconds could take almost a minute. Note: I am still connecting to AS
> 2000, with the 8.0 driver! Some nasty things are happening down there in
> driver hell. My performance profiler tells me it's all about the
> connection. The code line opening the connection is executing like a
> turtle on valium. There is almost no processor usage and memory is plenty.
>
> Now I reckon Microsoft let MSAS 2005 out of the box a bit to early, but
> please prove me wrong before I go nuts. Again.
>
|
|
|
|
|