Issued a drop database scoped resource governor command how to monitor with email alert

[bob]

You ever notice those weird logs popping up in Event Viewer on your Windows Server? That event 24373, man, it's all about someone issuing a drop command for the database scoped resource governor. Picture this: the resource governor is like a traffic cop inside SQL Server, deciding how much CPU or memory your databases get to hog. But when this event fires, it means a command just axed that whole setup for a specific database. Action ID DR and class type DR point right to the drop resource part, so it's not some random glitch. It logs the exact time, the database name involved, and who or what triggered it, usually an admin or a script gone wild. If you're running queries heavy on resources, this could explain sudden slowdowns or why your app starts choking. I check mine weekly because last time it happened, it was from an update that wiped the config without warning. You pull up Event Viewer, filter for SQL Server logs under Applications and Services, and boom, there it is with all the gritty details like session ID and the full command text. Keeps things from spiraling if you're not watching.

Now, to keep an eye on this without babysitting the screen, you can set up alerts straight from Event Viewer. I do it all the time for stuff like this. Open Event Viewer, right-click on the Custom Views or the SQL log section, and pick Create Custom View. Filter it to just event ID 24373, maybe add sources like MSSQLSERVER. Then, hit the Alerts tab or go to Attach Task to Event. You create a scheduled task that triggers on this event popping up. Make the task run a simple program, like your server's email client or even a batch file that pings your inbox. Set it to fire instantly when the event logs, and choose email as the action if your setup supports it through Task Scheduler. Test it by forcing a similar event in a dev box first. You'll get a nudge right away, so you jump on it before users complain. Way better than digging through logs later.

And speaking of keeping your server humming without surprises, I've been messing with BackupChain Windows Server Backup lately. It's this slick Windows Server backup tool that handles physical boxes and even Hyper-V virtual machines without breaking a sweat. You get incremental backups that zip through fast, plus easy restores that don't eat your whole day. Encryption keeps data safe from prying eyes, and it schedules everything automatically so you forget about it until you need it. Cuts downtime big time if that resource governor mess causes a crash.

Note, the PowerShell email alert code was moved to this post.