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 |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2003-07-04 : 08:09:44
|
| Alessandro writes "Hi My application is a three tear application, my web server is IIS 5.0 and my web application is compesed from VB6 component.The problem is that the my db connection that i see with the stored procedure sp_who2 in sql 2000 persis for some day.(This cause low performance).Why ?Thanks in advance " |
|
|
jasper_smith
SQL Server MVP & SQLTeam MVY
846 Posts |
Posted - 2003-07-04 : 12:24:44
|
| Connection pooling is generally a good thing. It's perfectly normal for the connection to remain in SQL Server because when you close your connection you are just returning it to the pool, the actual connection to SQL is not closed. If you use profiler you'll see when the next database request comes in there will be a call to sp_reset_connection before your SQL. When you say it's causing poor performance are these connections holding locks or are you seeing an ever increasing number of idle connections ? HTHJasper Smith0x73656c6563742027546f6f206d7563682074696d65206f6e20796f75722068616e6473203f27 |
 |
|
|
|
|
|
Connection Pooling