Home/ Questions/Q 8311409
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-08T19:48:24+00:00

When I’m creating a new SSIS package in the SQL Server Business Intelligence Development

  • 0

When I’m creating a new SSIS package in the SQL Server Business Intelligence Development Studio, the default ProtectionLevel is EncryptSensitiveWithUserKey, but the standard ProtectionLevel we want to use is DontSaveSensitive.

Does anyone know if there is a way to change the default ProtectionLevel value?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    2012 users rejoice

    SSIS 2012 allows for project-level setting of package protection level.

    enter image description here

    If I manually change the package protection level to something different from the project, it will fail when you attempt to run/build.

    Project consistency check failed. The following inconsistencies were detected: Package3.dtsx has a different ProtectionLevel than the project.

    So what’s a soul to do with 2005-2008R2?

    I have found the best approach is to create template packages, either in a project or in the actual visual studio install.

    After creating your base package, setting up logging, configuration, package protection level, etc, you then need to find a way to have people use it. If it’s project-based, I find it is important to have people regenerate package IDs after copying the package. BIDSHelper is wonderful for addressing this-simply right click on the package in the solution explorer and select Reset GUIDs. Otherwise, I have an annotation in my base package reminding developers to right click on the control flow, select properties and in the ID property, click <Generate New ID>

    If you choose to go establish templates from the “Add, New Item menu” (ctrl-shift-A) all you need to do is copy the package(s) into your template folder.

    • 0