◆ Microsoft SQL Server

Back up SQL database to local drive

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 'inventory_control' database to…+
Perform a full backup of the 'inventory_control' database to 'C:\TempDBBackups\inventory_control_full.bak'.
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 back up the 'marketing_campaigns' database to my local drive for offline analysis,…+
Before I back up the 'marketing_campaigns' database to my local drive for offline analysis, make sure the backup is compressed to save space and that it's encrypted so sensitive campaign data is protected even if my drive is compromised.
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 back up the 'legacy_archives' database to my local drive for an audit, but it…+
I'm trying to back up the 'legacy_archives' database to my local drive, but it keeps failing with a 'disk full' error, even though I have plenty of space.
I'm trying to back up the 'legacy_archives' database to my local drive for an audit, but it keeps failing with a 'disk full' error, even though I have plenty of space on C:. The audit is due Monday, and I can't proceed without this data. I'm afraid I'm missing something fundamental about how the backup process sees my local drive. What's the most likely reason for this error, and how can I get this backup done quickly?
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 need to create local backups for ad-hoc analysis or troubleshooting, but they…+
I frequently need to create local backups for ad-hoc analysis or troubleshooting, but they often consume too much space or take too long.
I frequently need to create local backups for ad-hoc analysis or troubleshooting, but they often consume too much space or take too long, impacting my workflow and system performance. What habit should I change to make these temporary local backups more efficient in terms of size and speed, without compromising data integrity?
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.