Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
hari_sql
Starting Member
22 Posts |
 Posted - 2010-06-03 : 09:23:26
|
| Hi,I have noticed that each time a new Query Editor window is opened from the SQL Management Studio, a new connection is created. This can be verified using:SELECT DB_NAME(dbid), COUNT(dbid) FROM sys.sysprocesses WITH (nolock)WHERE dbid > 0 GROUP BY dbidMy doubt is whether keeping multiple windows (containing queries) open like this (though most of them would be idle), would consume any system resource or lead to any performance issues of the DBs (assuming there are lots of other connections too coming in to the DBs from different applications).Any reply regarding this would be greatly appreciated.Thanks & Regards,Hari. |
|
|
Bustaz Kool
Master Smack Fu Yak Hacker
1834 Posts |
Posted - 2010-06-03 : 18:38:41
|
| My understanding is that the connection itself does consume a small amount of memory. I think about 1K per connection. If your connection is idle, I wouldn't worry about any real load on the system. Connection Pooling, after all, keeps connections open and actually improves performance.=======================================A couple of months in the laboratory can save a couple of hours in the library. -Frank H. Westheimer, chemistry professor (1912-2007) |
 |
|
|
|
|
|
SQL Server Active Connections