◆ Microsoft SQL Server

Upgrade SQL Server in-place

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 an in-place upgrade of the 'DevSQL01' database instance from version 2017 to 2019.…+
Perform an in-place upgrade of the 'DevSQL01' database instance from version 2017 to 2019. Ensure all existing databases and logins are migrated, and confirm application connectivity for the 'CRM_App' after the upgrade. Schedule this for the maintenance window on Saturday at 2 AM.
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 we upgrade the 'Reporting' SQL Server instance to 2019, make sure it's a low-risk…+
Before we upgrade the 'Reporting' SQL Server instance to 2019, make sure it's a low-risk operation. I need a clear rollback plan, a pre-upgrade checklist that identifies potential compatibility issues for our custom reports, and a post-upgrade verification script to confirm all services are running and data is accessible.
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 in-place upgrade of the 'Analytics' SQL Server instance from 2016 to 2019 failed halfway…+
The in-place upgrade of the 'Analytics' SQL Server instance failed halfway through the process.
The in-place upgrade of the 'Analytics' SQL Server instance from 2016 to 2019 failed halfway through, and now the instance won't start. The BI team needs their data for end-of-quarter reports by Monday morning. I'm afraid of data loss or extended downtime. I can't tell if it's a corrupted installer, a resource issue, or a pre-existing configuration problem. What's the likely diagnosis and the best next move to either complete the upgrade or roll back safely?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternOur in-place database upgrades consistently cause unexpected downtime or break critical…+
In-place SQL Server upgrades consistently cause unexpected downtime or application compatibility issues.
Our in-place database upgrades consistently cause unexpected downtime or break critical applications due to unforeseen compatibility issues. This leads to frantic late-night fixes and lost trust from business users. I'm losing credibility with IT management for not delivering smooth upgrades. What habit should I change in our planning and execution to ensure future in-place upgrades are reliable and minimally disruptive?
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.