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 - 2002-08-20 : 09:03:01
|
| Riley writes "We are using SQL 2000 for a client/server OLTP application. When monitoring the application from SQL Server Enterprise Manager we notice a large jump in the number of 'sleeping' processes when certain clients connect to the application. This jump does not happen for other clients running on the same OS platform and using the same application.The processes that are created do not cause any blocking problems but remain in the sleep status with a command of "Awaiting Command" until the user exits the application.Any hints on what causes sleeping processes to hang around would be greatly appreciated.TIA,Riley" |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2002-08-20 : 16:59:21
|
| try dbcc inputbuffer(spid) to see the last thing they executed.Can also use the profiler to see what happenned.also look at the connect times, last batch and io to see they have done anything.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
MichaelP
Jedi Yak
2489 Posts |
Posted - 2002-08-20 : 17:32:51
|
| It's possible those connections are "pooled" connections. If you are taking advantage of ADO connection pooling you might see that behavior.It's also possible that you are not closing your connections properly.The generally accepted way of comunicating with SQL server (at least with ADO) is to make the connection as late as possible, and close it as soon as possible.Michael<Yoda>Use the Search page you must. Find the answer you will.</Yoda> |
|
|
|
|
|
|
SQL Server Processes