◆ Microsoft SQL Server

Create a job in SQL Server using query

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 taskCreate a new SQL Server job named 'CleanOldLogs' that executes the 'DELETE FROM LogTable WHERE…+
Create a new SQL Server job named 'CleanOldLogs' that executes the 'DELETE FROM LogTable WHERE LogDate < DATEADD(month, -6, GETDATE());' query. Schedule it to run monthly on the first day of the month at 3 AM.
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 creating the new job to update customer loyalty scores, review the provided query.…+
Before creating the new job to update customer loyalty scores, review the provided query. Suggest improvements for performance, especially considering the large customer base, and add error handling to ensure data integrity even if the update fails mid-way. This job is critical for our marketing campaigns.
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 creating a new job to purge old transactional data, but the query provided by the business…+
I'm creating a new job to purge old transactional data, but the query provided by the business analyst seems overly complex and potentially inefficient.
I'm creating a new job to purge old transactional data, but the query provided by the business analyst seems overly complex and potentially inefficient for the volume of data. I'm afraid running it as-is will cause performance issues during off-peak hours, but I don't want to challenge their logic directly. What's the likely risk of this query, and what's the best way to suggest a more optimized approach without undermining their work?
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 create jobs with queries that later cause performance problems or unexpected data…+
I often create jobs with queries that later cause performance problems or unexpected data issues.
I often create jobs with queries that later cause performance problems or unexpected data issues, leading to emergency fixes and lost trust. I feel like I'm always reacting to these. What habit should I change in my process for validating and testing queries before incorporating them into critical automated jobs, to prevent these recurring headaches?
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.