Access front end creates many "sleeping" connection

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



I have Access 2003 MDB file as front end to a SQL server database. The
application is using DSN to connect to SQL server. All report and form
use passthrough queries or ODBC linked tables as the record sources.

Some forms / reports have 3 subforms and 2 comboboxes, but the
performance is fine.

When checking the current activities in Enterprise Manager, I realized
that for each client, there is about 5 connection to SQL server. Some of
them are "sleeping", some are "waiting for command".

I have 20 clients using Access front end, and the number of connections
become more than hundred, which slowdown the server.

I also check to make sure that using DSN with connection pooling, but I
do not understand why access automatically create many connection to SQL
server when it is supposed to have only 1? and not "Sleeping" or
"waiting" as I already close the form using this connection.

Thank for any comment, solution for this.

Trung



*** Sent via Developersdex http://www.developersdex.com ***
.



Relevant Pages

  • Re: Connection Error: ADO.Net and SQL Server 2005
    ... Hitchhiker's Guide to Visual Studio and SQL Server ... I can connect to the server through an ODBC connection ... It is very puzzling because this client doesn't seem to have anything ...
    (microsoft.public.sqlserver.connect)
  • RE: Error 17835 - When encryption and Shared Memory are enabled
    ... Did you encounter this error when you connected to your SQL Server ... Did your SQL Server instance use a certificate explicitly specified by ... you configure your client connection settings "Force Protocol Encryption" ...
    (microsoft.public.sqlserver.connect)
  • RE: Invalid authorization specification
    ... Does your application use a DSN to connect to SQL Server? ... DSN is setup correctly on the client machine. ... How to troubleshoot connectivity issues in SQL Server 2000 - ...
    (microsoft.public.sqlserver.connect)
  • Re: Losing connections with SQL 2005
    ... Hitchhiker's Guide to Visual Studio and SQL Server ... SQL Server automatically detects if the client falls into the sea or gets ... Does the Connection pooling mechanism do this on its ... Upgrading our app is a really big task, ...
    (microsoft.public.sqlserver.connect)
  • Re: netbios and named pipes sql replication.
    ... Once the client switched to named pipes, ... > connection with. ... > When we took named pipes support off the SQL server with the MS patch, ... > We had to manually walk thru the ODBC setup and configure the CLIENT ...
    (microsoft.public.sqlserver.replication)