preventing ssis from breaking dft target mappings

Question

hi we run 2014 enterprise. every once in a while before new table layouts are deployed to the next environment (eg qa) and because we like to put aliases in our connectors, ssis breaks already existing source to target mappings. Yes, it depends on what the alias points to. Is there a way to tell ssis to maintain all mappings in a dft regardless of issues it sees?

i believe these breaks only occur if we open the dft forgetting the alias is now in the connector. my head is saying to use that "defer error check" option (if its available on just one dft) but i dont know what the negative ramifications might be.

Answer 1

Hi @db042190 ,

I did some online research for you that we could change the SSIS connection managers while deploying the packages to different environments.

As said here.

The basis method for controlling and allowing to switch connections between DEV and PROD would be to handle it in Integration Services Catalog, under the SSISDB.

This allows you to create an enviroment called DEV under your DEV server and a environment called PROD on your PROD server. Each difference is that the variables has different connectionstrings, and hereby you never need to edit them into your SSIS project. So basically you can deploy your SSIS project to PROD with dev connectionstrings, but the environment will make sure it always points to your PROD connections.

Details you may refer:

https://www.sqlchick.com/entries/2015/1/4/parameterizing-connections-and-values-at-runtime-using-ssis-environment-variables

Regards，

Zoe

---

If the answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hot issues October

Answer 2

thx zoe, thats great for our future. but at present we are still running ssis from msdb, not the catalog. can you weigh in on a solution for that scenario?