Connection to Analysis services from VB - very slow

Dear All,

I noticed a strange problem with one of my client's computers where in establishing a connection with Analysis services from VB takes 6 seconds, when the computer is not connected to network, but it takes only a fraction of a second when the computer is in networ. We use ADOMD to connect to Analysis server. Analysis services is installed in the local machine.

I ran dependency walker and found that the dll WS2_32.dll (winsock dll) is taking most of the time when establishing connection.

This issue is very important for us and it would be great, if someone could help me in this.

Thanks in advance,

Niyas

Have you tried to use aternative machine name when connecting locally?

Try connecting to your Analysis Server using "localhost" or "127.0.0.1"

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights

|||

Hi Edward,

Thanks for your reply. I did try connecting to Analysis services using localhost, but there is no difference in the performance. I also created a machine level account (not in any domain) and tried connecting to Analysis services. But still, it does not show any difference.

This problem occurs in our client's machine alone and not in my computer or in my colleagues computers.

Thanks,

Niyas

|||

This might be related to VB initialization. Try posting your question on VB forum.

http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=32&SiteID=1

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Hi Edward,

I doubt whether this could be VB initialization problem, because the same problem occurred, when I tried to create a connection string using a .udl file. When I set the machine name, login credentials (Windows NT),driver and when I tested the conenction, it took 6 seconds, when I'm not in network and fraction of a second when I'm in network.

Thanks,

Niyas.

|||

Good. This is not VB related.

This is looks to be a general network problem. Try and see if you can find solution to this situation in windows networking forum. I doubt this is related to Analysis Services. Looks like generic connectivity problem.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

Connection to Analysis services from VB - very slow

Dear All,

I noticed a strange problem with one of my client's computers where in establishing a connection with Analysis services from VB takes 6 seconds, when the computer is not connected to network, but it takes only a fraction of a second when the computer is in networ. We use ADOMD to connect to Analysis server. Analysis services is installed in the local machine.

I ran dependency walker and found that the dll WS2_32.dll (winsock dll) is taking most of the time when establishing connection.

This issue is very important for us and it would be great, if someone could help me in this.

Thanks in advance,

Niyas

Have you tried to use aternative machine name when connecting locally?

Try connecting to your Analysis Server using "localhost" or "127.0.0.1"

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights

|||

Hi Edward,

Thanks for your reply. I did try connecting to Analysis services using localhost, but there is no difference in the performance. I also created a machine level account (not in any domain) and tried connecting to Analysis services. But still, it does not show any difference.

This problem occurs in our client's machine alone and not in my computer or in my colleagues computers.

Thanks,

Niyas

|||

This might be related to VB initialization. Try posting your question on VB forum.

http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=32&SiteID=1

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Hi Edward,

I doubt whether this could be VB initialization problem, because the same problem occurred, when I tried to create a connection string using a .udl file. When I set the machine name, login credentials (Windows NT),driver and when I tested the conenction, it took 6 seconds, when I'm not in network and fraction of a second when I'm in network.

Thanks,

Niyas.

|||

Good. This is not VB related.

This is looks to be a general network problem. Try and see if you can find solution to this situation in windows networking forum. I doubt this is related to Analysis Services. Looks like generic connectivity problem.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

Connection string to SQL Server database

I am a java programmer and currently developing a web application that is suposed to keep records of all Computers that are purchased or written off. I have my database sitting at MSSQL server express ed. 2005 and so far i only know to connect to Access DB. Can someone help me with the syntax to connect to MSSQL server.

reply to [email removed]

Quote:

Originally Posted by Java25

I am a java programmer and currently developing a web application that is suposed to keep records of all Computers that are purchased or written off. I have my database sitting at MSSQL server express ed. 2005 and so far i only know to connect to Access DB. Can someone help me with the syntax to connect to MSSQL server.

reply to Me

Check this site .. and you ll find the connections to all the existing databases in the world ;-) .. it really worked for me and I am using this for the past 4 yrs.

http://www.connectionstrings.com/

HTH..

Connection Problems

Hello,
I have a small workgroup of computers (4) all running windows xp sp2. One
of them is running msde2000. I can connect to a named instance of sql server
but can not connect to the default instance. I am using osql and using
trusted connection. I am not sure what other information is needed so
please do not hesitate to ask! I am really pulling my hair out on this one!
Any help would be greatly appreciated.
Hello,
Did you activated TCPIP network protocol for this default instance (verify
in the error.log for the instance)?
Hope this will help.
Philippe RUELLO
DBA MSSQL
"Michael O'S" <mroresolutions@.woh.rr.com> a crit dans le message de news:
NhMxd.3864$mA3.1811@.fe2.columbus.rr.com...
> Hello,
> I have a small workgroup of computers (4) all running windows xp sp2. One
> of them is running msde2000. I can connect to a named instance of sql
> server but can not connect to the default instance. I am using osql and
> using trusted connection. I am not sure what other information is needed
> so please do not hesitate to ask! I am really pulling my hair out on this
> one!
> Any help would be greatly appreciated.
>
|||Are you sure there is a default instance? If it's just MSDE 2000, there
usually is not a default instance. It installs to a named instance by
default. Look in Administrative Tools/Services for all SQL Server services.
See if you have any running besides the named instance.
"Philippe RUELLO" <pruello@.tibco.fr> wrote in message
news:uReN1wF7EHA.2124@.TK2MSFTNGP15.phx.gbl...
> Hello,
> Did you activated TCPIP network protocol for this default instance
(verify[vbcol=seagreen]
> in the error.log for the instance)?
> Hope this will help.
> --
> Philippe RUELLO
> DBA MSSQL
> "Michael O'S" <mroresolutions@.woh.rr.com> a crit dans le message de news:
> NhMxd.3864$mA3.1811@.fe2.columbus.rr.com...
One[vbcol=seagreen]
needed[vbcol=seagreen]
this
>
|||Thank you for your input! I did check tcpip settings and all were good. I
did however find in the server logs that some intances (including the
default) were not listening or failing to bind to port 1433.
I ended up removing msde instance that I could not connect to and
reinstalling making sure to use the DISABLENETWORKPROTOCOLS=0 parameter.
After I did this, I could see all instances of msde on any computer from any
computer in my workgroup.
Good Luck!
"Michael O'S" wrote:

> Hello,
> I have a small workgroup of computers (4) all running windows xp sp2. One
> of them is running msde2000. I can connect to a named instance of sql server
> but can not connect to the default instance. I am using osql and using
> trusted connection. I am not sure what other information is needed so
> please do not hesitate to ask! I am really pulling my hair out on this one!
> Any help would be greatly appreciated.
>
>

Connection Problem - MSDE 2000 on Peer to Peer Network

I have MSDE installed on one of my computers in my peer to peer network (all
computers XP Professional). All computers on the network can see each
other. However, I cannot use Query Analyzer or Enterprise Manager to
connect to MSDE except from the computer that contains MSDE.
Is it possible to connect to MSDE using Query Analyzer etc, in this
scenario.
ThanksI'll be honest, I have yet to work with MSDE but here are some links that
may help
http://support.microsoft.com/defaul...kb;en-us;319930
http://support.microsoft.com/defaul...kb;en-us;325003
HTH
Ray Higdon MCSE, MCDBA, CCNA
--
"Sid Sarin" <sidsarin123@.earthlink.net> wrote in message
news:zByYb.9378$W74.78@.newsread1.news.atl.earthlink.net...
> I have MSDE installed on one of my computers in my peer to peer network
(all
> computers XP Professional). All computers on the network can see each
> other. However, I cannot use Query Analyzer or Enterprise Manager to
> connect to MSDE except from the computer that contains MSDE.
> Is it possible to connect to MSDE using Query Analyzer etc, in this
> scenario.
> Thanks
>|||By default, MSDE 2000 SP3 only has shared memory (LPC) enabled. To allow
connections from remote machines you have to enable TCP and/or named pipes
through the server network utility (svrnetcn.exe).
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.