◆ Microsoft SQL Server

Set up database monitoring and alerting

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts
See the prompt↓All Microsoft SQL Server tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskEnable basic monitoring for the new HR database, HR_PROD, so we can track its disk space usage…+
Enable basic monitoring for the new HR database, HR_PROD, so we can track its disk space usage and connection count. We need to catch any immediate issues.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptWhen setting up monitoring for the new customer portal database, make sure it's easy to see…+
When setting up monitoring for the new customer portal database, make sure it's easy to see when critical thresholds are crossed. I need to quickly identify if we're running low on disk space or if the CPU is spiking, without digging through logs.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe new analytics database is going live next week, and I'm supposed to have monitoring in…+
The new analytics database is going live next week, and I'm supposed to have monitoring in place, but I'm worried about false positives overwhelming me.
The new analytics database is going live next week, and I'm supposed to have monitoring in place, but I'm worried about false positives overwhelming me. Last time, the finance director was annoyed by constant 'disk full' alerts that weren't actually critical. I don't know what thresholds are truly important for this new workload. What's the best way to configure alerts so I only get notified for real problems?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI spend too much time manually checking system health instead of relying on automated alerts. I…+
I spend too much time manually checking server health instead of relying on automated alerts.
I spend too much time manually checking system health instead of relying on automated alerts. I often miss subtle issues that build up over time until they become critical. What habit should I change to proactively set up effective monitoring for new databases, so I'm not constantly reacting to emergencies?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Microsoft SQL Server's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.