◆ Microsoft SQL Server

Implement data obfuscation

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
See the prompt↓All Microsoft SQL Server tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskApply the data obfuscation script to the customer production database, specifically the…+
Apply the data obfuscation script to the customer production database, specifically the 'CreditCardNumber' and 'SSN' columns in the 'Customers' table, ensuring it runs during the next maintenance window on Tuesday between 2 AM and 4 AM, and confirm completion.
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 roll out this new obfuscation script to the main production environment, I need to…+
Before we roll out this new obfuscation script to the main production environment, I need to make sure it won't break anything. Can you run it against the staging database and provide a report on any data type mismatches or performance impacts it might cause, especially for the 'Transactions' table?
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 new data obfuscation script failed on the test host, throwing a 'data truncation' error for…+
The new data obfuscation script failed on the test server with a 'data truncation' error.
The new data obfuscation script failed on the test host, throwing a 'data truncation' error for the 'CustomerFeedback' table. I'm afraid this could corrupt existing data if we push it live, and the compliance deadline is next Friday. The lead developer, Sarah, thinks it's a minor schema issue, but I suspect a larger data integrity problem. What's the most likely diagnosis here, and what's the safest next step to avoid data loss and still meet the deadline?
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 finding new data fields that need obfuscation after the initial rollout, leading to…+
I keep finding new data fields that need obfuscation after the initial rollout.
I keep finding new data fields that need obfuscation after the initial rollout, leading to repeated emergency changes and missed compliance checks. We're losing credibility with the security team. What habit should I change to ensure a more comprehensive initial assessment and avoid these reactive, last-minute additions?
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.