Quantcast
Channel: SQL Server Integration Services forum
Viewing all articles
Browse latest Browse all 24688

Project deployment to test and production

$
0
0

Hi!

We have the development and test server on one domain and the production server on different domain. I am not allowed to create thrust between the domains.

I create a .ispac file that is deployed to the test server with protectionLevel for the project set to EncryptSensitiveWithPassword. When testing is finished I want to get the project in to production. My prefered method would be to go to the production server right click the folder Integration Services Catalogs --> SSISDB--> Projects, chose Deploy Project and then chose Integration Services catalog in the wizard to connect directly to the test server and get the project.

But it seems this is impossible because of the different domains.

My next solution was to open the test server right click the folder Integration Services Catalogs --> SSISDB--> Projects--> <name of project>, chose Export and export the project to an .ispac file. Then copy the file from the test server to production and then deploy the package on the production server. But it seems that when I export the file on the test server the project is automaticly encrypted with the user key belonging to the user exporting the data, so when I copy the file to the production domain the user is different and I get an error that all the nodes could not be decrypted. Is it easy/possible to change the protectionLevel and set a password for all files in an ispac file so I can use this method to deploy?

My last choice is to deploy the same .ispac file as was deployed to test. This works fine, but is not preferred.


Viewing all articles
Browse latest Browse all 24688

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>