MSDE access over network slow for XP workstations, not Win2K -- sql server msde

sql server msde : MSDE access over network slow for XP workstations, not Win2K

Jim K
12/28/2004 11:12:55 AM

I've installed MSDE SP3a on a Windows 2000 Server, and the VB6 client
application on multiple workstations.
These workstations are either Win2000 Pro or WinXP Pro (both SP1 and SP2).

All workstations can access and ping the server under 1MS.

When the client application opens and reads data from the database server,
it takes a short time for this to be performed on the Win2000 Pro machines,
but all the XP machines take an abnormally long time to connect and to
retrieve the data.
The XP's do connect, but the retrieval is very slow, sometimes it timesout
during a retrieval.

This occurs even when nobody is connected to the database, so I've ruled out
the governer.

I'm using ADO to connect and all PC's have MDAC 2.7 or greater.
The install process only installed MDAC 2.7 if the current version is before
that.

Anybody have an idea what might be the problem?
All responses are welcome.

TIA
Jim K

Jim K
12/30/2004 9:21:26 AM

Thanks, I didn't think of that.

I have connected using the IP in other apps, but that was to the default
instance.

Since I have a named instance in this case, how would I format the IP and
instance?

Ex: default instance installed on server SERVER1, I can substitute the IP
for SERVER1
for named instance SERVER1/DB1, how would I format the IP? IP#/DB1 ?

Thanks!

[quoted text, click to view]

Greg Low [MVP]
12/30/2004 8:20:08 PM

Hi Jim,

Name resolution problems perhaps? Try connecting to the IP address instead
of the server name to find out.

HTH,

--
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com

[quoted text, click to view]

Greg Low [MVP]
12/31/2004 8:40:48 AM

Hi Jim,

I'd suggest setting a fixed port for the named instance, then just connect
to that port. Even set up an alias on the client boxes that knows about the
port. It would completely avoid the sql browser function that essentially
just maps your instance name to a port anyway. To do that:

1. Open svrnetcn.exe and for the named instance, uncheck the "dynamic port"
box and select your own port (ie 38474 or something).
2. Restart the instance.
3. On the client, run cliconfg.exe and set up an alias pointing to that port
on the server.

HTH,

--
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com

[quoted text, click to view]

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages about sql server msde

home · blog · groups

Questions? Comments? Contact the dn