◆ Microsoft SQL Server

Create SSIS packages in SQL Server

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 taskCreate an SSIS package named 'DailySalesImport' that extracts data from the 'Staging.SalesRaw'…+
Create an SSIS package named 'DailySalesImport' that extracts data from the 'Staging.SalesRaw' table, transforms the 'OrderDate' column to datetime format, and loads it into 'Production.SalesFact'.
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 build a new SSIS package for our weekly financial report data. Make sure it's robust…+
I need to build a new SSIS package for our weekly financial report data. Make sure it's robust and easy for the finance team to understand if there's an error. It should handle messy input data gracefully and log any rows that fail validation, so they can quickly see what needs fixing.
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 SSIS package for the 'CustomerFeedback' import keeps failing on the production environment…+
My SSIS package for the 'CustomerFeedback' import keeps failing on the production server, but it runs perfectly on my development machine.
My SSIS package for the 'CustomerFeedback' import keeps failing on the production environment with a 'data conversion error' on the 'Comments' column, but it runs perfectly on my development machine. The data source is a CSV file from marketing, and they just updated their template. I'm afraid I'll miss the Monday morning deadline for the executive dashboard. What's the most likely difference between environments causing this, and how can I quickly diagnose and fix it?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI spend too much time debugging SSIS packages that break due to minor data changes or…+
I spend too much time debugging SSIS packages that break due to minor data changes or environment differences.
I spend too much time debugging SSIS packages that break due to minor data changes or environment differences between development and production. This is costing me credibility with the business users when reports are late. What habit should I change to build more resilient SSIS packages from the start, especially regarding data validation and configuration management?
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.