◆ Microsoft SQL Server

Re-add user after moving database

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 taskRe-add the user 'susan.jones' to the 'MarketingDB' database after it was moved to the new…+
Re-add the user 'susan.jones' to the 'MarketingDB' database after it was moved to the new host.
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 acceptAfter we moved the 'SalesData' database to the new 'SQL_CLUSTER_02' host, re-add all the users…+
After we moved the 'SalesData' database to the new 'SQL_CLUSTER_02' host, re-add all the users who had access previously. Make sure their permissions and roles are identical to what they had on the old host, so the sales team can access their reports without interruption on Monday morning.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentDavid from the executive team can't access the 'Executive_DashboardDB' after we moved it, even…+
A critical user can't access a database after a migration, even though I thought I re-added them correctly.
David from the executive team can't access the 'Executive_DashboardDB' after we moved it, even though I re-added his user account. I'm worried I missed a specific permission or a linked database setting. What's the most common reason a re-added user still lacks access after a database move, and what should I check first to get David online before his 9 AM meeting?
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 move a database, I get a flurry of calls from users who can't access it, even…+
After every database migration, I inevitably get calls about users who can't access the moved database, indicating a recurring issue in my re-addition process.
Every time I move a database, I get a flurry of calls from users who can't access it, even after I've re-added them. This suggests a pattern of missing steps or misconfigurations. What habit should I change in my database migration process to ensure all users are correctly re-added with their proper access from the start, avoiding these post-migration headaches?
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.