Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a legacy app that connects to my SQL 2008 server. I'm trying to determine if the application is re-using it's connection to the SQL server or is creating new connections on a regular basis.

Using SQL Profiler I've audited for login events, but that appears to generate an event every time a SQL statement is executed even with apps that I know are maintaining their connection to SQL.

share|improve this question
Have you tried filtering on the LoginName/ApplicationName being used by your legacy app? – jl. May 4 '10 at 21:32
up vote 1 down vote accepted

sp_who will give you a list of connections.

share|improve this answer
  1. What you do is try setting the max pool size on the server and then open a few connections to the server and see if it times out, but then again that's if you want to see if the pool is being used.

  2. Use perfmon to check. Here is some info on that ADO.NET Perfmon counters

Here is another link you may find interesting SQL Server Connection Pooling

Hope that helps.

Edit - Also you may want to check the driver information on the legacy app, example if the legacy app is using an OLEDB driver, they may have some notes on the connection pooling.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.