◆ Microsoft SQL Server

Check status of running SQL Server jobs

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 taskShow me all the database agent jobs that failed in the last 24 hours and give me their error…+
Show me all the database agent jobs that failed in the last 24 hours and give me their error messages. I need to know what broke overnight.
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 report on the status of our critical overnight jobs, list any that are still running…+
Before I report on the status of our critical overnight jobs, list any that are still running past their usual completion time, or any that have failed multiple times this week. I need to flag potential issues before they become actual problems.
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 daily data load job for the marketing team didn't run last night, and they're asking why…+
The daily data load job for the marketing team didn't run last night, and they're asking why their dashboards are empty.
The daily data load job for the marketing team didn't run last night, and they're asking why their dashboards are empty. The job history shows 'Unknown error'. I'm worried it's a permissions issue that will take all morning to track down. What's the most common reason a scheduled job suddenly fails with a generic error, and what's the quickest way to restart it or get some data into their dashboards?
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 job statuses every morning, and often miss smaller…+
I spend too much time manually checking job statuses every morning.
I spend too much time manually checking job statuses every morning, and often miss smaller issues until someone complains. What habit should I change to get a consolidated, actionable view of job health first thing, so I can spot trends and intervene before failures impact business users?
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.