Why so many SQL Server Connections?

[SpyderMan1234]

I have a SQL Server 2005 server which exists to only run 1 application. Late yesterday, when activity would have been mininal, I set up an alert to notify me of the number of SQL user connections. This morning the number of user connections has ballooned up to 135 and counting. However, when I go to the host application, it tells me that only 14 users are logged in. So what on Earth are the other 121 user connections for? Is the application not dropping idle SQL connections as it should? Is this normal? The only other thing I could think of would be the backup routines I have scheduled, but it's only a daily full backup and an hourly differential. Any ideas??

Thanks in advance!

Jeff

P.S. Since I've been typing this message, it has grown to 143.

 

[calico]

HI,

With SQL 2000, we have similar problem.

application not dropping idle SQL connections as it should
OR
debugging tool still activated on production

Calico

 

[mrdenny]

Well SQL will use a bunch for it's internal processes. SPIDs 0-50 are reserved for system processes. You can also exclude any processes which are running under the sa account from the SQL Server directly. These would also be system processes. If you are using the service broker this will also be using processes.

Depending on the way the application was written each use who logs into the application could require many database connections. If those connections are not closed correctly then they would remain open until the client application is closed.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

My Blog