4

We are in the process of migrating our servers to a new data center. Currently we are on SQL Server 2014 and SSIS packages deploy in seconds.

The new data center has several SQL server 2016 installs and I noticed that on some of them the "Changing protection level" takes a very long time (around 7 minutes!) but on some it is fast. When I change the SSIS project's TargetServerVersion to 2016 the changing protection level is slow on all new servers.

The ProtectionLevel of the project and packages is set to (and has been) to DontSaveSensitive.

What is causing the slowness and how can I troubleshoot this? It eventually does deploy without any errors.

Improve this question
1
  • 1
    It is already set to "DontSaveSensitive" in Visual Studio. The process is slow even when I deploy to sql server with no packages present in the catalog.
    – Artur W
    Commented Nov 18, 2019 at 19:27

1 Answer 1

Reset to default
2

It seems that I solved my own problem. I do not know exactly what cause it, but here is what i did.

It turns out that only one of the projects that we have had the problem I described. That project happened to have multiple packages included. For testing I removed all packages from the project and added one at the time, built the project after each step and tested the deployment. They all worked fine individually and ultimately I ended up with a project with all packages that deploys fast.

This got me thinking that maybe the project file/build files got hosed somehow and they all needed a full refresh/rebuild.

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.