Oh geez. I feel quite operatic in the sense of this article lately 😛

The sysadmin here decided a few weeks back that the CPU usage of the SQL Server was just too high after midnight, which just so happens to be the time when things like full backups, DBCC checks, statistics updates, and index rebuilds are done. Without informing he, he started restarting the server at around 1:00 A.M., right in the middle of all the maintenance work.

Today, he calls me and tells me about the problems, and says the maintenance stuff is making the CPU too high. I question why that's a problem, since everyone's off-premises, and the jobs finish by 7:00 A.M., and work for the day starts at 9:30 A.M. Plenty of leeway. "Well, the CPU is just too high! It's bad for the server!" Alright, well, the CPU will come down eventually, especially if you stop restarting the server every day, which forces recompilation on everything- "No! That's not it! There must be something on the SQL side of things messing it all up!" Well, technically, yes, if there wasn't interference with the processes meant to control that, and also, we don't have backups anymore since they haven't been allowed to run- "It's better this way!" ... *Sigh*.

I'm not looking forward to the final act, which will probably involve corruption and a few dead databases :hehe: