◆ Microsoft SQL Server

Merge a subset of a target table

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 taskI need to merge the new customer data from the staging table `Staging.NewCustomers` into the…+
I need to merge the new customer data from the staging table `Staging.NewCustomers` into the `Production.Customers` table. Only include customers from the 'North Region' and ensure existing records are updated while new ones are inserted. Make sure the merge completes by Friday's EOD.
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 merge this customer data into production, make sure it handles potential duplicates…+
Before I merge this customer data into production, make sure it handles potential duplicates gracefully without errors. I need to see a report of any rows that would cause a conflict or be skipped, so I can review them with Mark from Sales before the final merge.
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 customer merge just failed, leaving me unsure about the state of the `Production.Customers`…+
The merge of new customer data failed halfway through, and I'm not sure if it rolled back cleanly or left partial data.
The customer merge just failed, leaving me unsure about the state of the `Production.Customers` table. I'm afraid I might have introduced inconsistencies or lost some updates. How do I quickly verify if the table is in a stable, consistent state, and what's the safest way to proceed with the remaining data without causing more issues?
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 losing hours to merge failures because of unforeseen data type mismatches or constraint…+
I keep losing time when merges fail due to unexpected data types or constraints, forcing me to restart from scratch.
I keep losing hours to merge failures because of unforeseen data type mismatches or constraint violations, forcing me to roll back and restart. This impacts our reporting deadlines. What habit should I change to better anticipate these data quality issues before I even attempt the merge, saving me rework and keeping our data reliable?
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.