October 30, 2007 at 3:15 pm
We have recently deployed our database application on a new client site.
The application runs on 20 PC's (Windows XP) connected to an SQL Server 2005 running on a Windows Server 2003 on the same network.
The application (VB6) connects to the SQL Server via a system DSN (ODBC Sql Server Driver) defined on each PC.
Problem
The application is often loosing it's connection to the SQL Server especially when it has been idle for more than 5-10 mins.
The error message returned to the application is:
Communication link failure
I have looked for a possible option or setting in sql server 2005 that might be causing this but this doesn't seem to be the case.
What would be the best and most effective way to find out what is causing the connections to drop ?
Thanks.
October 31, 2007 at 10:00 am
You can run some traces from the client machines through the ODBC Data Source Administrator.
You might also want to check the connection time out setting on the SQL Server.
You might look into connection pooling as well.
Here's a decent article about ODBC connection pooling it specifically mentions VB.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply