August 31, 2016 at 4:49 pm
We have some SSIS packages in SSIS catalog on test server. I need to move them to production server.
Is it the same thing as I do for other user database?
I just need to do a backup on test server, and restore and overwrite existing production SSISCatalog(currently there is no packages in the SSIScatalog on prod, it is newly enabled)
Is this correct?
I don't need to recover some encryption keys or related , correct? Those keys confused me.
Thanks,
September 1, 2016 at 1:49 am
You should leave the catalog db alone and simply redeploy the packages.
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
September 1, 2016 at 11:54 am
Ok, will think this as a best practice.
But just prepare for cases like we don't have the original source code, or the developer no longer works here, then we need to restore all packages from one server to another, should we go through this process of restore from dev to production,
if so, it goes back to my original question.
Thanks,
September 2, 2016 at 8:28 pm
Not even then. Instead, export the packages from SSISDB, put them into VS projects and build/deploy from there.
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply