asked
How do I ensure SSISDB package and MSDB package are the same?
Hi everyone. I am new to package execution from external references, so this is basically a newbie question. Up until now, I have been deploying all of my packages from SSDT directly to SSISDB and then scheduling them to run from there in the SS Agent. I have a new requirement of executing packages from external references. It took me a while to figure out how to even get the package to MSDB. The only way that I was able to get a package deployed into MSDB was to connect to Integration Services in SSMS, right click to import a package, browse out to the package that I saved on the network, and add it. So my first question is: Is there a better, or more efficient way, to deploy my package to MSDB? My follow up question is: How do I ensure that the package that I have deployed to MSDB is exactly the same as the package that was deployed to SSISDB from Visual Studio? In this one case, I am sure because I am the only one working on this right now, but if we are deploying to two different locations with a disconnect in where the deploy is happening from, I can see that mistakes are bound to happen. Any recommendations on how you make sure MSDB and SSISDB stay in sync would be helpful. Thank you!
I have a master package in a separate project that uses the external reference. I also have an Agent job calling the package from SSISDB. I was thinking maybe I should not ever deploy to SSISDB, but the msdb deployment doesn't seem to allow any structure so the packages can't be organized in any meaningful way. How do you have your system setup? Do you only deploy to msdb? Thank you for your response!
18 People are following this question.
