◆ Microsoft SQL Server

Determine event information from SQL Server

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 taskFind out why the 'Order Processing' stored procedure failed last night at 2 AM. The finance…+
Find out why the 'Order Processing' stored procedure failed last night at 2 AM. The finance team needs to know if any orders were lost.
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 we roll out the new 'Inventory Update' process, set up better event monitoring for it. I…+
Before we roll out the new 'Inventory Update' process, set up better event monitoring for it. I need to quickly identify any failures and understand the context, not just that it failed, so we can troubleshoot effectively.
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 nightly data synchronization job failed again, and the logs are just saying 'error…+
The nightly data synchronization job failed, but the logs are vague about the actual cause.
The nightly data synchronization job failed again, and the logs are just saying 'error occurred'. I'm afraid I can't tell if it was a network glitch, a data issue, or something more serious. Our operations team is waiting for an update, and I don't know how to give them a clear picture without more specific event information. What's the likely diagnosis and the best next move to pinpoint the exact failure?
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 constantly spending hours digging through fragmented logs and various tools to piece…+
I spend too much time digging through fragmented logs to diagnose database issues.
I'm constantly spending hours digging through fragmented logs and various tools to piece together what happened during a database incident, wasting critical response time. I need a more centralized and comprehensive way to capture event information. What habit should I change to make diagnosing database issues faster and more accurate?
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.