◆ Microsoft SQL Server

Perform daily SQL Server administration activities

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 taskBack up the Production database to the \backup_share\Monday folder. Verify the backup completes…+
Back up the Production database to the \backup_share\Monday folder. Verify the backup completes successfully and record the completion time in the daily log.
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 the end of the week, review the database error logs for the past 24 hours across all…+
Before the end of the week, review the database error logs for the past 24 hours across all production instances. Identify any recurring errors or warnings that indicate potential instability or resource contention, and suggest specific actions to investigate or resolve them before they escalate.
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 ETL job failed for the third time this week, and the data warehouse team is now…+
The nightly ETL job failed for the third time this week, and the data warehouse team is now blocked from running their morning reports.
The nightly ETL job failed for the third time this week, and the data warehouse team is now blocked from running their morning reports. I'm afraid of breaking something worse by trying to restart it without knowing why it keeps failing, but the pressure to get the data flowing is immense. What's the most likely recurring cause for a nightly job failure, and what's the safest first step to diagnose and potentially resolve it without causing further delays?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI frequently get pulled into urgent 'system is down' or 'job failed' incidents, often due to…+
I frequently get pulled into urgent 'system is down' or 'job failed' incidents, often due to issues that could have been prevented.
I frequently get pulled into urgent 'system is down' or 'job failed' incidents, often due to issues that could have been prevented with better foresight. This reactive approach creates stress and impacts service availability. What habit should I change to proactively monitor system health and job statuses, identifying potential failures and addressing them before they impact users or critical business processes?
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.