Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
imStuck
Starting Member
8 Posts |
 Posted - 2006-09-08 : 01:24:55
|
| Hi, im developing the front end of an sql server database in vb.net When the front end is run each day, the first database information call seems to lag alot for all users, each user has a client side front end. This lag is usually around 3-5seconds. I dunt know what causes this lag, i would like to speed it up. any suggestions? My thoughts were that the server has to setup a session connnection for each user each day, but the server is never stopped, so i dunno. Does Sql keep the users information in memory for a few hours and then flushes it or something? |
|
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
Posted - 2006-09-08 : 03:17:08
|
| is it slow for each user as they connect, or is it slow for the first user to connect?if it is slow for the first user to connect, you may have autoclose enabled. Right click the database in Enterprise Manager and select properties and then the options tab. Make sure that autoclose is not selected.-ec |
 |
|
|
imStuck
Starting Member
8 Posts |
Posted - 2006-09-10 : 18:33:19
|
| It is slow for each user to connect. That autoclose option is off also. |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2006-09-11 : 06:53:30
|
| Probably worth checking that the ADO version on all Clients, and the Server, is up to date.Might there be some DNS round-the-houses to actually locate the server? No sure how you would find it if there is - tracert maybe?Kristen |
|
|
|
Rishi Maini SQL2K5 Admin
Yak Posting Veteran
80 Posts |
Posted - 2006-09-11 : 07:17:57
|
| There can be number of issue for the same:- A.) Network ( as suggested earlier by Kristen)Ping the SQL Server Box by name from your client Box and check if the ping command takes 3-5 Secs to start getting response back first time from the SQL Server.If that is the case may be adding the SQL Name in the "hosts" file may help to fasten the initial communication between the Clients and the Server.B.) If I understand correctly you see the delay once users start their applciation. So the question is what exactly your application does apart from making a connection to SQL. Does it also populate some kind of data in the front page that it needs to pull from SQl server ? C.) Check if creating a ODBC connection from the Cleint pointing to SQL Server and hitting "Test Connection" also takes 3-5 secs. If not then its certainly the way you have configured your application (Point B) D.) Cehck if creating a TCP/Ip Alias along with the port on which SQL is listening on the Clients helps to fasten the communication.ThanksRishi Maini |
|
|
|
|
|
|
1st connection slow