October 18, 2005 01:18 PM
Keep Your Packages in the Dark
Use these 4 tips to create machine-independent SSIS packages
Rating:

(0)
SQL Server Magazine
InstantDoc ID #47688
Picture this: You've just finished building a package in SQL Server Integration Services (SSIS). You've tested it with various inputs, and everything seems to work fine. You have error handling just right, you share packages that isolate common logic as subpackages, you've got event handlers that notify you of problems in the package or that handle error output from the dataflow task. Your dataflow task is screaming fast and everything is running without a hitch in your development environment. Then, you move your package to the production server and everything breaks. You're getting errors everywhere and nothing seems to work. Sound familiar?
SSI...
...This article is for paid Professional Members only.
Already a Professional Member? Please log in now: