Sunday, March 25, 2012

@@connections

I currently get 47 million connections back when I run 'select @.@.connections'. At what point does this become a problem with memory? And, how can I close connections from the backend? I know stopping and restarting will do it but that is not always possible. Any ideas? Thank You

You're not interpreting this number correctly. @.@.connections returns the total number of connections that have been made or attempted since SQL Server was last started. It has no relation whatsoever to the number of open or active connections.

To see or count open connections, execute sp_who or sp_who2.

|||Thanks for clearing that up. The mem usage for our sqlserver is at 3 gig, is that normal?sql

No comments:

Post a Comment