◆ Microsoft SQL Server

Migrate SQL Server databases

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 taskMove the 'CustomerData' and 'OrderHistory' databases from the old database 2017 instance to the…+
Move the 'CustomerData' and 'OrderHistory' databases from the old database 2017 instance to the new database 2022 cluster by Friday. Ensure all logins and user permissions are transferred correctly, and verify data integrity after the move.
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 start migrating the 'Inventory' and 'Sales' databases to the new cluster, list the…+
Before I start migrating the 'Inventory' and 'Sales' databases to the new cluster, list the potential compatibility issues for stored procedures and deprecated features between database versions 2017 and 2022. Also, suggest a rollback plan for each database in case of failure.
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 'CustomerData' database migration aborted at 60% completion. The application team is seeing…+
The 'CustomerData' database migration failed halfway through, and now the application team is calling.
The 'CustomerData' database migration aborted at 60% completion. The application team is seeing connectivity errors, and I'm not sure if the partial data on the new database instance is corrupted or if the old database instance is still accessible. What's the fastest way to diagnose the state of both databases and get CustomerData back online, even if it means reverting to the old database instance temporarily?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep underestimating the time needed for database migrations because of unforeseen…+
Migrations often take longer than expected because of unexpected dependencies or permissions.
I keep underestimating the time needed for database migrations because of unforeseen dependencies and permission issues that only surface during the move. What habit should I change in my pre-migration checks to better anticipate these problems and provide more accurate timelines to the project managers?
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.