posted on Wednesday, February 16, 2005 4:19 PM
by
Knight_Reign
Managing complexity in packages?
<<Yeah, I know. I'm blogging a lot today. I've had a few backed up since .Text has been tweaky lately.>>
We've had several customers send mail asking what was the best way to approach some common problems, which are basically, “How do I organize my complex packages so that they're easier to manage?”
You've got a few options:
- Use more containers - That's what they're there for, to reduce complexity. Especially the sequence container.
- For large dataflows, find logical intervals where you can stage into raw adapters. Enhances restartability.
- Use more subpackages - This is the ultimate because you can share the packages in different solutions. (Code reuse) Faster design time as well. Easier to debug child packages alone than large packages.
- Use property expressions - A lot of folks are using script tasks for simple things like catenating strings etc. Use property expressions for these types of simple jobs instead.
- Use enable/disable options on containers to isolate pieces of a package while debugging.
These are just a few examples of ways you can eliminate complexity in your IS solutions.
Thanks
Universe.Earth.Software.Microsoft.SQLServer.IS.KirkHaselden