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 |
|
abhwhiz
Starting Member
37 Posts |
 Posted - 2007-09-14 : 11:18:48
|
| Why do we have lot of sleeping jobs on the server? Does SQL Server clean them up? Does SQL come back (to execute) to these processes after some time? Does SQL server has a "Garbage Collector" to do this?Do we need to clean them up manually? |
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2007-09-14 : 13:32:43
|
| what do you mean sleeping jobs?jobs will be there after set up or run unless you configure it to delete itself after run or manually delete ityou can also automate it but the main reason for jobs is to automate routines that are recurring like periodic tasks--------------------keeping it simple... |
 |
|
|
Zoroaster
Aged Yak Warrior
702 Posts |
Posted - 2007-09-14 : 14:26:24
|
When you say jobs do you mean connections? If there are connections that linger it is often to do with the application that opens but then doesn't close them.
Future guru in the making. |
|
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-09-14 : 23:31:26
|
| Connection pooling leaves connection open so app can reuse it, that saves time. |
|
|
|
abhwhiz
Starting Member
37 Posts |
Posted - 2007-09-15 : 10:59:40
|
| It was a bit stupid on my part not to checkfor typos before i posted.It was indeed sleeping processes. I am really sorry for the confusion created. Thanks a lot for replies. |
|
|
|
|
|
|
Sleeping Jobs