◆ Microsoft SQL Server

Detect securities fraud and market abuse

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 taskRun the fraud detection script for all trades executed on April 15, 2024, specifically looking…+
Run the fraud detection script for all trades executed on April 15, 2024, specifically looking for wash trading patterns. Output the results to a CSV file named 'fraud_report_20240415.csv' and place it in the secure reports directory.
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 hand this fraud detection report to legal for review, make it easier for them to grasp…+
Before I hand this fraud detection report to legal for review, make it easier for them to grasp the severity. Highlight the top five riskiest accounts by total suspicious trade value, and add a column showing the percentage of their daily trading volume flagged as suspicious. Also, ensure the timestamps are in UTC for consistency with other evidence.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe automated fraud detection just flagged a cluster of small, highly correlated trades across…+
The latest fraud detection run flagged an unusual number of small, correlated trades from multiple accounts.
The automated fraud detection just flagged a cluster of small, highly correlated trades across several accounts, all executed within seconds of each other. This feels different from the usual wash trading. I'm worried it's a new, more sophisticated manipulation, but I don't want to raise a false alarm to compliance. What's the most likely explanation for this pattern, and what's my best next step to quickly validate if it's a genuine threat or a system anomaly?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI'm spending too much time sifting through low-value, low-impact false positives in our daily…+
I keep getting buried in false positives for low-value trades, wasting time investigating noise.
I'm spending too much time sifting through low-value, low-impact false positives in our daily fraud detection reports. It delays getting critical alerts to the compliance team. What habit should I change in how I configure or review these reports to focus immediately on high-risk, high-impact anomalies without missing genuine threats, so I can improve my efficiency and credibility with compliance?
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.