◆ Microsoft SQL Server

Perform SQL Server backup and restore

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 taskRestore the 'ProductionDB' database to the state it was in at 2:00 PM yesterday, February 28th,…+
Restore the 'ProductionDB' database to the state it was in at 2:00 PM yesterday, February 28th, using the full and transaction log backups. Place it on the staging database for the dev team.
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 restore ProductionDB for the dev team, make sure it won't impact our ability to…+
Before I restore ProductionDB for the dev team, make sure it won't impact our ability to recover to a later point if needed. Identify the earliest point in time we can restore to without losing critical data, and confirm the full backup from Sunday is valid.
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'm trying to restore ProductionDB to the staging database, but it keeps failing with a generic…+
The restore process for ProductionDB failed, but the logs are vague about the exact cause.
I'm trying to restore ProductionDB to the staging database, but it keeps failing with a generic error, and the dev team is waiting. I suspect a corrupted backup file or an issue with the recovery model, but I'm not sure which. What's the fastest way to diagnose the specific problem and get this restore completed?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternRestoring databases, especially ProductionDB, always feels like a high-wire act, taking too…+
Database restores are often complicated and take longer than expected, especially for critical systems.
Restoring databases, especially ProductionDB, always feels like a high-wire act, taking too long and causing anxiety. I'm worried about missing a step under pressure. What habit should I change to make our restore process more reliable and less stressful, ensuring we can always meet RTOs?
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.