◆ Microsoft SQL Server

Copy table ignoring identity property

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 taskCopy all data from the 'OldProducts' table to the 'NewProducts' table, ensuring that the…+
Copy all data from the 'OldProducts' table to the 'NewProducts' table, ensuring that the identity column values from 'OldProducts' are preserved in 'NewProducts'.
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 migrate the 'LegacyCustomers' table to the new 'Customers' table this weekend, write…+
Before we migrate the 'LegacyCustomers' table to the new 'Customers' table this weekend, write a script that copies all data, including the existing customer IDs, and handles any potential data type mismatches or constraint violations during the transfer, so the CRM team doesn't lose historical customer references.
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 need to copy a subset of orders from the 'ProductionOrders' table to a 'StagingOrders' table…+
I need to copy a subset of orders from the 'ProductionOrders' table to a 'StagingOrders' table for testing, preserving the original OrderIDs, but the identity column on 'StagingOrders' keeps auto-incrementing, creating new IDs. The QA team needs exact duplicates for their test cases, and I'm afraid of breaking their scripts if the IDs don't match. I don't know if there's a simpler way than manually disabling and re-enabling identity. What's the best next move to copy the data with original IDs efficiently and safely?
I need to copy a subset of orders from the 'ProductionOrders' table to a 'StagingOrders' table for testing, preserving the original OrderIDs, but the identity column on 'StagingOrders' keeps auto-incrementing, creating new IDs. The QA team needs exact duplicates for their test cases, and I'm afraid of breaking their scripts if the IDs don't match. I don't know if there's a simpler way than manually disabling and re-enabling identity. What's the best next move to copy the data with original IDs efficiently and safely?
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 struggle with copying data between tables while preserving identity values, often…+
I frequently struggle with copying data between tables while preserving identity values, often leading to manual workarounds.
I frequently struggle with copying data between tables while preserving identity values, often leading to manual workarounds. Where do I keep losing time and accuracy? What habit should I change in my approach to data migration and replication tasks involving identity columns, so I can consistently and efficiently transfer data without losing original identifiers or resorting to complex, error-prone steps?
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.