Hi Jason,

You mentioned below usage

"A more typical setup would be to store the packages in msdb on this SSIS server (you're paying for the license anyway) or to just store the packages on some network share. My preference is to store them in msdb on the SSIS server."

I have 5 packages in which 3 packages are inside 1 package and other package is a stand alone package. Currently we are running it in single SQL server ( for both database and SSIS). We are in server upgrade and have 2 servers now ( development and testing phase now)-one for SSIS and another for database. we deployed the packages into msdb on new SSIS server. when i tried to run( open msdb in SSIS server and right click on package name and run) the package it failed in the step where it calls a child package. Then i opened the package in BIDS and opened the execute package task for the child package. I opened the task and checked the package location under SQL Server option and I couldnt find any packages under MSDB.( In current environment where we have only one server so we were able to select the packages under MSDB without giving server details). Then I created a new connection for SSIS server and tried to get the package but getting error. Then I imported the package to MSDB under Database server and I was able to select package under MSDB of Database server for child package location. That means for selecting a package location for a child package under SQL Server option (other option is file system which we are not using) we need to import the package in to MSDB under Database server? Then what is the use of MSDB under SSIS server other than running the packages which are also needed to be deployed under MSDB of database server. Please help. Because of this error we are thinking of having only one server for both SSIS and database again.

Thanks

Ajeesh