◆ Microsoft SQL Server

Add unique constraint ignoring existing violations

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 taskAdd a unique constraint named 'UQ_ProductCode' to the 'ProductCode' column in the…+
Add a unique constraint named 'UQ_ProductCode' to the 'ProductCode' column in the 'Inventory.Products' table, ignoring any existing duplicate rows.
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 enable this unique constraint on the 'ProductCode' column, ensure that any ignored…+
Before I enable this unique constraint on the 'ProductCode' column, ensure that any ignored duplicates are logged somewhere for review by the data governance team, and that the constraint won't impact existing applications that might be inserting duplicates.
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 added a unique constraint to the 'ProductCode' column ignoring existing violations, but…+
I added a unique constraint, but now some data imports are failing, and I don't know if it's due to new duplicates or the old ones.
I just added a unique constraint to the 'ProductCode' column ignoring existing violations, but now the nightly product import from the supplier is failing. I'm afraid this will halt inventory updates and impact sales. I can't tell if the import is trying to insert new duplicates that are now being rejected, or if the 'ignore_dup_key' option didn't work as expected with the existing bad data. What's the most likely cause, and how can I quickly diagnose if the constraint is the actual blocker without rolling back the change?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI frequently implement data integrity constraints that, despite my best intentions, cause…+
I often introduce data integrity constraints that unexpectedly break existing applications or data flows.
I frequently implement data integrity constraints that, despite my best intentions, cause unforeseen disruptions to existing data imports or applications. This leads to emergency fixes and erodes trust with the operations team. What habit can I change to better anticipate and mitigate the downstream impact of schema changes and constraint additions before they go live?
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.