问题
I've got a windows service that regulary (every 10 sec) does a lot of db activity. I've verified that all my connections are closed (using using). After some time (days or hours) I get this error:
Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occured because all pooled connections were in use and max pool size was reached.
I found that I should check the sysprocesses table, and found that it is creating lots of new entries when my code is run (and I'm really sure I'm closing the connection)
Question is: In my case, where it is the same user doing the same queries all over, should there be a new entry for almost every tick in the service? Other services does not have this behaviour.
Or is maybe looking in the sysprocesses table not giving me any useful info?
Larsi
回答1:
sysprocesses is deprecated so if you're on 2005+ use sys.dm_exec_requests, sys.dm_exec_connections and sys.dm_exec_session.
that'll give you better info about your connections.
来源：https://stackoverflow.com/questions/7388006/sysprocesses-table-will-it-help-me-debug-connection-pooling-issues