◆ Microsoft SQL Server

Maintain client credit history

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 taskUpdate customer account 78901's credit limit to $25,000, effective immediately. Ensure the…+
Update customer account 78901's credit limit to $25,000, effective immediately. Ensure the change is logged in the audit trail for compliance.
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 the quarterly credit review meeting, generate a report showing all customers whose…+
Before the quarterly credit review meeting, generate a report showing all customers whose credit history has changed from 'Good' to 'Warning' or 'Critical' in the last 90 days. Include the reason for the change, the date, and the assigned credit analyst, so the team can prioritize follow-up.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentA major client, 'Global Innovations,' is suddenly showing a 'Critical' credit risk, but our…+
A major client, 'Global Innovations,' is suddenly showing a 'Critical' credit risk, but our sales team insists they just paid a huge invoice.
A major client, 'Global Innovations,' is suddenly showing a 'Critical' credit risk, but our sales team insists they just paid a huge invoice. I'm afraid of wrongly halting their next order and damaging the relationship, but I can't find any recent payment data in the credit history system. What's the most likely reason for this discrepancy, and what's the best next step to quickly reconcile the information without causing alarm?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI often spend too much time manually cross-referencing payment records with credit history…+
I often spend too much time manually cross-referencing payment records with credit history updates when discrepancies arise.
I often spend too much time manually cross-referencing payment records with credit history updates when discrepancies arise, leading to delays and frustration for the sales team. This 'detective work' slows down critical decisions. What habit should I change to better synchronize payment processing with credit history updates, minimizing manual intervention and ensuring a single, accurate view of client financial standing?
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.