◆ Microsoft SQL Server

Join a table with a table valued function

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 taskJoin the 'Orders' table with the results from the 'GetOrderItemsByDate' function for January…+
Join the 'Orders' table with the results from the 'GetOrderItemsByDate' function for January 15, 2024, on the 'OrderID' column. I need to see all order details combined with their specific items for that day.
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 acceptWhen joining the 'Customers' table with the 'GetCustomerAddresses' function, make sure to…+
When joining the 'Customers' table with the 'GetCustomerAddresses' function, make sure to handle cases where a customer might not have an address in the function's output. I need all customers to appear in the final dataset, even if their address is null, for the marketing team's report.
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'm attempting to join the 'Products' table with the 'GetProductCategories' function to get…+
I'm trying to join 'Products' with a 'GetProductCategories' function, but the join is returning far too many rows, suggesting a mismatch.
I'm attempting to join the 'Products' table with the 'GetProductCategories' function to get product-category mappings, but the result set is unexpectedly huge. I suspect the join condition on 'CategoryID' isn't unique in one of the sources or the function is returning duplicate categories for a product. Our inventory report is due by end of day, and I'm afraid of generating incorrect data. What's the most likely diagnosis for this explosion of rows, and what's the best next step to correctly join these two so the report is accurate?
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 run into performance bottlenecks or incorrect data when joining large tables with…+
I often struggle with performance issues or incorrect results when joining tables with table-valued functions, especially with large datasets.
I frequently run into performance bottlenecks or incorrect data when joining large tables with table-valued functions, particularly when the function's output isn't indexed or optimized. This slows down report generation and leads to rework. What habit should I change to ensure these joins are consistently efficient and accurate, especially when dealing with high-volume data, so I can deliver reliable results faster?
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.