Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged integration to Master #3

Merged
merged 15 commits into from
Aug 16, 2018
Merged

Merged integration to Master #3

merged 15 commits into from
Aug 16, 2018

Conversation

fenngineering
Copy link
Owner

No description provided.

fmms and others added 15 commits March 11, 2018 14:18
To deploy into the data factory support for SQL Authentication is needed. So far the connection string was hard coded to use integrated windows authenticated for SQL Server on premise.
When one copies a dtsx package in the solution explorer. The name is not updated right away in the updated package. One has to open the package and change something or rename it. Otherwise the project contains two packages with the same Name attribute in dtproj file. This made ssis-build.exe crash.
EncryptSensitiveWithUserKey is the default and thus used by many developers. I found out that the DTS:ProtectionLevel attribute in the dtsx file is only set if it differs from EncryptSensitiveWithUserKey.
…iveWithUserKey

Added ProtectionLevel.EncryptSensitiveWithUserKey when a new password…
@fenngineering fenngineering merged commit d76b5de into master Aug 16, 2018
fenngineering added a commit that referenced this pull request Aug 17, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants