◆ Microsoft SQL Server

Get last identity inserted in a 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 get the ID of the new customer record I just added to the Customers table. It's…+
I need to get the ID of the new customer record I just added to the Customers table. It's critical for linking their first order. Get me the last identity value inserted into the Customers table.
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 add these 500 new product records, I need to reliably capture each new product's ID…+
Before I add these 500 new product records, I need to reliably capture each new product's ID right after insertion so I can immediately update our inventory system. Help me set up a way to get the last identity inserted for each new product, making sure it's accurate even if other users are adding data at the same time.
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 inserted a new record into the 'Orders' table, but the application crashed before I…+
I just inserted a new record into the 'Orders' table, but the application crashed before I could grab the new OrderID.
I just inserted a new record into the 'Orders' table, but the application crashed before I could grab the new OrderID. I'm afraid I might get the wrong ID if someone else also inserted an order in the last few seconds, which would mess up our customer's history. How can I be absolutely sure I retrieve the exact OrderID for the record I just inserted, and what's the safest way to do it right now?
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 track of new record IDs when I'm doing bulk inserts or when the application…+
I keep losing track of new record IDs when I'm doing bulk inserts or when the application unexpectedly closes.
I keep losing track of new record IDs when I'm doing bulk inserts or when the application unexpectedly closes, leading to data inconsistencies and wasted time manually fixing links. What habit should I change to consistently and reliably capture the identity of newly inserted records, especially when I'm working quickly or under pressure?
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.