◆ Microsoft SQL Server

Implement SQL Server Integration Services

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 taskDeploy the 'SalesData_ETL.dtsx' package to the 'SSISDB' catalog on 'ProdSQL01'. Configure it to…+
Deploy the 'SalesData_ETL.dtsx' package to the 'SSISDB' catalog on 'ProdSQL01'. Configure it to run daily at 3 AM, using the 'SalesUser' credential, and set up an email notification to 'ETL_Alerts' on package failure.
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 off the 'Customer_Data_Sync' package to the operations team, make sure it's…+
Before I hand off the 'Customer_Data_Sync' package to the operations team, make sure it's robust and easy to monitor. I need it to log detailed errors, restart gracefully on transient failures, and expose key performance metrics so they can quickly spot issues without digging into complex logs.
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 'Inventory_Update' SSIS package failed last night, and the inventory reports are now…+
The 'Inventory_Update' SSIS package failed last night, and the inventory reports are now showing stale data.
The 'Inventory_Update' SSIS package failed last night, and the inventory reports are now showing stale data. The operations manager is calling, asking why their stock numbers are off. The error message is 'Data conversion failed for column 'Quantity''. I'm afraid this will impact order fulfillment. I can't tell if it's a source data issue, a package configuration problem, or a data type mismatch. What's the likely diagnosis and the best next move to get this package running successfully?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternOur SSIS packages frequently fail in production due to unexpected data changes or environment…+
Our SSIS packages frequently fail due to unexpected data changes or environment differences, requiring manual intervention.
Our SSIS packages frequently fail in production due to unexpected data changes or environment differences between dev and prod, requiring constant manual intervention. This causes delays in critical data availability and frustration for business users. I'm losing time constantly debugging these issues. What habit should I change in how I design, test, and deploy SSIS packages to make them more resilient and reliable?
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.