Hi, I have a small Point of Sale app that has two pc's running on a local network.
pc "A" is running XP Home Ed and has SQL Express installed with the SP1 and Express Mgr.
pc "B" is also XP Home Ed and just has a client app installed.
A has SQL express with TCP and Named Pipes open so that B can connect and access the data.
the CSLA app when run on A connects fast - ok.
on B it seems to be very slow, I found and fixed one problem with the sql express config but still seems slow...
the DB is *NOT* a user-instance so it should be connected and ready like a big SQL install.
after the inital connection is made it's ok, things work fine.
just that on startup there is a lag I want to get rid of.
I'm looking at my code and startup to see if I can tweak things but it seems like the SQL connection is the place that is a problem....
any ideas ??
I have seen something similar.
I think the connection is inspecting your network to find the server.
This may be the cause for the delay.
Perhaps editng your hosts file to let the system know that servername="A" translates to IP address 10.0.0.12 could help.
Joe
Yeah, that's partly what I was thinking...
I found that the server had been configured funny, the local nic was on a 192.168.1.xxx subnet but sql config listed a tcp/ip address of 10.10.xx.xx ! now why sql was not complaining I do not know!
also the client did have an lmhosts but just for fun I edited the connection from foo to 192.168.1.xxx
same idea as you had -- hit the address not the name!
that did seem to fix it!
I was just wondering if SQL express was perhaps not keeping the db live or some such...
looks like the name lookup was killin it on connection!
Copyright (c) Marimer LLC