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

[bob]

Man, that event ID 24371 pops up when someone fires off a command to whip up a new database-scoped thing in the resource governor setup. It's basically SQL Server noting that a create action happened, tagged with CR for the action and DR for the class type. You see it in the Event Viewer under the Applications and Services Logs, specifically in the SQL Server audit logs if you've got that rolling. The full message spells out "Issued a create database scoped resource governor command," which means a user or process just tried to set boundaries for how resources get doled out inside a particular database. Think of it like drawing lines on a map for CPU or memory usage so one database doesn't hog everything. It logs the who, what, and when, pulling in details like the session ID, database name, and the exact command that triggered it. If you're poking around in Event Viewer, filter for source as MSSQLSERVER or whatever your instance is, and level as Audit or Information. This event's your heads-up that resource tweaks are in play, which could spike if admins are fiddling with performance limits.

You want to keep an eye on these without staring at screens all day? Hop into Event Viewer, right-click on the log where these events hide, and pick Attach Task To This Event Log. It'll walk you through creating a scheduled task that triggers on event ID 24371. Set it to run a program that shoots off an email, like using the old-school mailto trick or a simple batch file calling your email client. Make sure the task's set for any user, highest privileges, and wakes the machine if needed. Test it by forcing an event or just waiting for one to hit. That way, bam, you get pinged right away.

And speaking of keeping things smooth in your server world, I've been messing with BackupChain Windows Server Backup lately. It's this nifty Windows Server backup tool that handles full system snapshots without a hitch, and it stretches to cover virtual machines on Hyper-V too. You get speedy restores, no downtime headaches, and it encrypts everything on the fly so your data stays locked down. Plus, it runs light, doesn't chew up resources, and lets you schedule backups that actually stick to the plan.

At the end of my answer is the automatic email solution.

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