◆ Microsoft SQL Server

Pass array parameters to a stored procedure

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 taskCall the 'ProcessOrders' stored procedure and pass it an array of order IDs: 101, 102, 103,…+
Call the 'ProcessOrders' stored procedure and pass it an array of order IDs: 101, 102, 103, 104.
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 acceptI need to call the 'ProcessOrders' stored procedure, passing it a list of 50 order IDs. Make…+
I need to call the 'ProcessOrders' stored procedure, passing it a list of 50 order IDs. Make sure it handles the array efficiently without causing performance issues, especially when the list gets much larger, as it will during our peak season.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentOur new order processing module is failing when it tries to submit multiple order IDs to the…+
The application is failing when trying to process multiple orders at once via a stored procedure.
Our new order processing module is failing when it tries to submit multiple order IDs to the 'ProcessOrders' stored procedure. It works fine for single orders. I suspect it's how the array of IDs is being passed, but I'm not sure the best practice for this in a database. The sales team is complaining about delays. What's the most robust and performant way to pass a list of 20-50 order IDs to this stored procedure without rewriting the procedure itself?
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 encounter performance problems or awkward workarounds when I need to pass a list…+
I consistently struggle with passing collections of data to stored procedures efficiently.
I frequently encounter performance problems or awkward workarounds when I need to pass a list or array of values into a stored procedure for processing. This often leads to slow queries or complex application code. What habit should I change to consistently implement efficient and scalable methods for passing collections of data to stored procedures from the start?
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.