◆ Microsoft SQL Server

Monitor and alert on SQL Server issues

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

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskSet up an alert for when the 'SalesDB' transaction log usage exceeds 80% for more than 15…+
Set up an alert for when the 'SalesDB' transaction log usage exceeds 80% for more than 15 minutes, notifying the 'DBA_Team' distribution list.
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 acceptBefore I set up this alert, make sure it's actionable and won't generate too much noise.…+
Before I set up this alert, make sure it's actionable and won't generate too much noise. Consider the historical log usage patterns for 'SalesDB', suggest a more dynamic threshold if appropriate, and flag any other related metrics that should be included in the alert message for context.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI just got paged at 2 AM about the production database instance being unreachable, but none of…+
I just got paged at 2 AM about the production server being unreachable.
I just got paged at 2 AM about the production database instance being unreachable, but none of my standard monitoring alerts fired before the outage. I'm afraid I missed a critical precursor event that could have prevented this, and I don't know if my current alerts are comprehensive enough. What's the most likely diagnosis for the silence, and what's my best next move to ensure I'm alerted to potential issues before they become full outages?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI'm often the last to know about critical database issues, usually from angry users or other…+
I'm often the last to know about critical database issues, usually from angry users.
I'm often the last to know about critical database issues, usually from angry users or other teams, feeling constantly behind. I spend too much time manually checking dashboards and logs. What habit should I change to proactively monitor and alert on database issues, so I'm always aware of problems before they escalate?
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.