SSIS Package Organization - Best Practices

I am currently using SSIS to load an ODS.  Each SSIS package contains the code to load one ODS table and none of the packages are dependent on each other.  What would be the best approach to maximize re-usability reduce development and maintenance time?  Should I keep the packages in their own separate solutions file or move all of the packages into one solution file?  I have about 60 ODS packages in total.
Who is Participating?
HoggZillaConnect With a Mentor Commented:
For maintability, putting them in one package is clean and neat. However, most of the time I keep all of the packages independent and create a master package to call the "child" packages using the Execute Package Task.
In the end, personal preference.
If you are asking whether to keep all of the files in BIDS project solution, definately - assuming they are related.
HoggZillaConnect With a Mentor Commented:
SSIS is so call you could load the name of all your child packages into a database table. Read the data into a recordset, (object variable), put the recordset as the object for a Foreach Loop Container. Put a single Execute Package Task in the Foreach Loop Container and define the Package to run using an expression that is read from the loop of your table. For 60 packages that could change in number over time, this would be a very dynamic solution and not too difficult.
liv2007Author Commented:
Thanks HoggZilla.  I like your technique of calling the independent packages from a master package.  I'll try that.
Very welcome. Let me know if you need any help.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.