February 10, 2020 at 6:37 pm
Have not had luck searching on this.. must not be picking the correct words:
So we have upgraded our first SSIS server to SQL Server 2016 and Visual Studio 2017, using the Integration Services Catalog. Now in our older SSIS packages we use the "Rely on server storage and roles for access control." Also when opening up a package we never got decrypt error messages. This will occur in 2017 if you are not the same user that last saved the package AND on the same server/PC that saved the package. So how does one avoid this now?
February 10, 2020 at 6:53 pm
In my opinion, this does not sound like a robust development environment.
Your packages, together with projects and solutions, should be in source control. They should also be deployed to servers from source control. When you want to edit a package, use the source control version as the base, make your modifications, test and check in to source control.
Set the package protection level to Don't Save Sensitive.
Configure the values of sensitive parameters using SSISDB environments. These should also take care of the values of various connection strings and other environment-specific items.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
February 10, 2020 at 9:14 pm
Not saying we shouldn't push our vendor to support source control.. but we work mostly in their application making changes, and then the SQL side to support those changes. Heck they don't even support MTP. All the work we do in Dev, except for the SQL, has to be re-done in their application in both QA and Prod. I have been pushing them to fix that for years now.
I will look into trying to see what we can set up in the SSISDB .. like you brought up above. Thanks.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply