Occasionally, we run into problems with a long-running process turning into an extremely long-running process because SQL Server puts the process to sleep for long periods. Every so often, the process with wake up and get a little bit more CPU time, then it goes back to sleep. This seems to happen mostly with some of our cursor-driven processes when the number of rows is pretty large. It also seems to be somewhat load-dependent. I think I saw something about this once somewhere in the knowledge base, but I would like to know more about what SQL Server is doing and how to make it leave the process alone. Frequently, the process would complete in 10-15 minutes if left to run, but the periodic hibernation causes the job to run for a couple hours. As a note, with smaller processes, I have gotten SQL Server to leave processes like this alone by switching from a cursor to a pseudo-cursor, e.g. a while loop with select top 1, etc. Thanks.