Using Bids Helper to deploy is changing package protection level.
-
Has anybody used Bids Helper to deploy an SSIS package to the MSDB database? Three times I have used Bids Helper to deploy and it has changed the package protection level from DontSaveSensitive to EncryptSensitiveWithUserKey. This is causing an issue and I am wondering why this is occurring. I'm using SSIS 2008 with SQL Server 2008 R2. I couldn't find anywhere to set the project protection level. Any suggestions are welcome. Thank you.
-
karen.ferrara (9/20/2016)
Has anybody used Bids Helper to deploy an SSIS package to the MSDB database? Three times I have used Bids Helper to deploy and it has changed the package protection level from DontSaveSensitive to EncryptSensitiveWithUserKey. This is causing an issue and I am wondering why this is occurring. I'm using SSIS 2008 with SQL Server 2008 R2. I couldn't find anywhere to set the project protection level. Any suggestions are welcome. Thank you.This may be something you need to raise on the BIDS Helper forum. (http://bidshelper.codeplex.com/discussions)
Looking at the code (http://bidshelper.codeplex.com/SourceControl/latest#bidshelper/SSIS/DeployPackagesPlugin.cs) - and I must preface this by saying that I'm not exactly an expert here - this bit:
process.StartInfo.Arguments = string.Format("/FILE \"{0}\" /DestServer {1} /COPY {2};\"{3}\" /Q", sFilePath, newOptions.DestinationServer, sDestType, sDestFolder + sFileName.Substring(0, sFileName.Length - ".dtsx".Length));sBatFileContents.Append("\"").Append(process.StartInfo.FileName).Append("\" ").AppendLine(process.StartInfo.Arguments);process.Start();It seems that it doesn't set an ENCRYPT option when it calls Dtutil.exe so the default will be used (EncryptAllWithUserKey) - (https://support.microsoft.com/en-gb/kb/906562)
I think that you can output a .bat file with BIDSHelper. You could then edit this and rerun it to deploy your packages with the correct encryption level. For a guide on using dtutil, have a look at the following: https://msdn.microsoft.com/en-us/library/ms162820.aspx
I'm on LinkedIn -
I tried another approach to my deployment today. I connected to Integration Services from SSMS and then used the import package feature there to import the package. When I exported it the protectionlevel had changed from "DontSaveSensitive" to "EncryptSensitiveWithUserKey" so now I don't think it is a BIDS Helper issue.
-
karen.ferrara (9/21/2016)
I tried another approach to my deployment today. I connected to Integration Services from SSMS and then used the import package feature there to import the package. When I exported it the protectionlevel had changed from "DontSaveSensitive" to "EncryptSensitiveWithUserKey" so now I don't think it is a BIDS Helper issue.If you import a package, there's an option to select the protection level. Was it configured to "Keep protection level of the original package"?
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP -
Yes, it was. I think I found the issue. When I export the package, it is defaulting the protection level to "EncryptSensitiveWithUserKey" and I need to change this to "DontSaveSensitive".
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply