Hello All, I can't quite figure this one out and am hoping for some insights that I'm missing. I've got a batch statement that's seemingly waiting around for CPU resources when there are plenty available. The batch statement in question runs without issue if I execute it in SSMS, however when called through the application it will wait with SOS_SCHEDULER_YIELD for more than 30 minutes. There's not a lot of processing being done on the server at this time and it's on it's own dedicated connection. I just don't understand it! I can even execute the batch statements through SSMS while the other one is waiting! Help!! We recently moved this database from a 2000 environment to 2005. The 2000 environment did not see this same issue, but serviced the same application. The new environment is much better hardware as well, we've basically doubled the available CPU resources and increased memory by > 4x.