◆ Microsoft SQL Server

Back up and restore database to new 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 taskRestore the 'sales_reporting' database from the backup file 'sales_reporting_20231026.bak' to…+
Restore the 'sales_reporting' database from the backup file 'sales_reporting_20231026.bak' to the new 'analytics_server_02' instance, renaming the database to 'sales_archive_Q3'.
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 acceptWhen I restore the 'dev_environment' database to the new staging system, ensure that all user…+
When I restore the 'dev_environment' database to the new staging system, ensure that all user logins and permissions are also transferred correctly, and that the restored database is immediately available for testing without further manual steps.
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 restored the 'HR_payroll' database to the new system for disaster recovery testing, but…+
I just restored the 'HR_payroll' database to the new server, but users are reporting missing data from yesterday, and I can't figure out if I used the wrong backup file or if the restore process itself failed silently.
I just restored the 'HR_payroll' database to the new system for disaster recovery testing, but users are reporting missing data from yesterday, and I can't figure out if I used the wrong backup file or if the restore process itself failed silently. Our compliance depends on accurate payroll data, and I'm terrified we've lost critical information. What should I check first to diagnose this, and what's the safest way to re-attempt the restore?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternEvery time I have to restore a database to a new system, it takes longer than expected due to…+
Every time I have to restore a database to a new server, it takes longer than expected due to unforeseen issues.
Every time I have to restore a database to a new system, it takes longer than expected due to unforeseen issues like permission mismatches or missing linked connections, delaying critical project timelines. What habit should I change to consistently make these backup and restore operations smoother and more predictable, reducing the risk of unexpected delays?
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.