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?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Steve HoggITCommented:
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.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Steve HoggITCommented:
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.
Steve HoggITCommented:
Very welcome. Let me know if you need any help.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.