Re: SQL 2000 SP4 on Server 2003 SP1 not dropping connections

Sounds like you now using connection pooling which will always keep x many
connections to SQL Server even though the app closes the connection. This is
usually a desirable feature.


--
Andrew J. Kelly SQL MVP

"Brad Martin" <brad@xxxxxxxxxxxxx> wrote in message
news:1D06C303-485E-4843-9443-948FB9AB7B8E@xxxxxxxxxxxxxxxx
We recently upgraded our SQL 2000 SP3 instance (running on Windows 2000)
to SQL 2000 SP4 running on Windows Server 2003 SP1. The migration went
fine but we are now experiencing a problem where connections are not
dropping once the application is finished with it. The application is a
COM+ app making an ODBC connection, which then never closes. We are
running a job that cleans up the connections, but we can't seem to find
the reason why SQL is keeping the connections open in the first place.
Any ideas or suggestions?

Brad


.

Relevant Pages

  • Re: Dot Net 2.0 or SQL Server 2005 problem?
    ... Assume the SQLExpress set up is OK, whther you can actually access the SQL ... After installing SQL Server Express, if you did not add any SQL login ... Configuration' and set the option to 'Using Both TCP/IP and Named Pipes'. ... under the default settings SQL Server does not allow remote connections. ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: MS SQL 2005 Configuration ???
    ... It sounds like you are running SQLExpress, not SQLServer. ... I don't have SQL Express, so I can't replicate what you're seeing. ... "Surface Area Configuration for Services and Connections", ... SQL Server Browser). ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: SQL Server 2005 Express Connection
    ... Some people have been having issues when trying to make remote connections ... networking protocols are disabled by default in SQL Server Express. ...
    (microsoft.public.sqlserver.connect)
  • Re: Winforms v webforms?
    ... Windows app Offline/Online mode - you would have to do additional ... SQL Server connections - i am not too sure, ... windows client with web services on a server to fix this problem). ...
    (microsoft.public.dotnet.general)
  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... I moved every table I was able to move to the SQL ... closed connections - but all of these errors are in the version which used ... the SQL Server 2000 and everything worked ... communication between ODBC (OLEDB and Native Client, ...
    (microsoft.public.sqlserver.connect)
Loading