◆ Microsoft Azure

Query between databases in SQL Azure

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 Azure tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskWrite a T-SQL query that joins customer data from the 'Customers' table in the 'CRM' database…+
Write a T-SQL query that joins customer data from the 'Customers' table in the 'CRM' database with order details from the 'Orders' table in the 'Sales' database, both in a SQL database, to show customer names and their total order amounts.
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 query between the 'CRM' and 'Sales' databases in a SQL database to get customer order…+
I need to query between the 'CRM' and 'Sales' databases in a SQL database to get customer order history. Before I finalize this, make sure the query handles potential performance issues for large datasets, especially if 'Orders' has millions of rows, and flag any security implications of linking these two databases.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentMy cross-database query between 'CRM' and 'Sales' is running extremely slowly, and the sales…+
My cross-database query between 'CRM' and 'Sales' is running extremely slowly, and the sales team needs the report by EOD.
My cross-database query between 'CRM' and 'Sales' is running extremely slowly, and the sales team needs the report by EOD. I'm afraid of impacting production performance further if I keep trying different approaches, and I can't tell the sales manager, David, that I'm stuck. What's the most likely bottleneck for slow cross-database queries in a SQL database, and what's the quickest way to diagnose and improve its performance without causing downtime?
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 optimizing cross-database queries, leading to slow reports and…+
I frequently struggle with optimizing cross-database queries, leading to slow reports and frustrated users.
I frequently struggle with optimizing cross-database queries, leading to slow reports and frustrated users, which impacts my credibility with the business analysts. This often results in me spending hours tweaking queries that should be simple. What habit should I change to more effectively design and optimize cross-database queries in a SQL database from the start, avoiding these performance pitfalls?
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 Azure'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.