◆ Microsoft SQL Server

Back up a database using a SQL query

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 taskPerform a full backup of the 'Marketing_Data' database to the default backup location right…+
Perform a full backup of the 'Marketing_Data' database to the default backup location right now. We need a fresh copy before the data migration starts.
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 nightly backup runs for the 'Finance_Reports' database, ensure it's configured for…+
Before the nightly backup runs for the 'Finance_Reports' database, ensure it's configured for compression and verifies the backup's integrity. The finance director needs to know their data is safe and recoverable if something goes wrong.
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 a frantic call from the development team; they accidentally deleted critical data in…+
I just got a frantic call from the development team; they accidentally deleted critical data in the staging environment, and they need a restore from yesterday's backup.
I just got a frantic call from the development team; they accidentally deleted critical data in the staging environment, and they need a restore from yesterday's backup. I know we have backups, but I'm not sure if the last successful one for that specific database was actually complete or if it's even accessible from the current system. I'm afraid of telling them I can't recover it. What's the fastest way to confirm the integrity and location of yesterday's backup for the 'Dev_Staging' database?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI often find myself scrambling to verify backups only when a restore is urgently needed, which…+
I often find myself scrambling to verify backups only when a restore is urgently needed, which is too late.
I often find myself scrambling to verify backups only when a restore is urgently needed, which is too late. This always adds stress and delays when the pressure is highest. What habit should I change to proactively confirm the integrity and recoverability of all critical database backups on a regular basis, so I'm always confident they'll work when I need them?
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.