1

I'm trying to deploy around 20 SSIS packages which use SSIS project level connections to my SSIS server. The problem is that when I import them to the SSIS server they loose their connection.

It only works when i convert the project level connections to package level connections, but I want to avoid this since this would be inconvenient because all packages use the same connection.

Does someone know a fix for this?

Adriaan
  • 17,741
  • 7
  • 42
  • 75
Walnussbär
  • 567
  • 5
  • 19
  • Check out [this thread](https://stackoverflow.com/questions/39888087/what-is-environment-variable-configuration-in-ssis-and-what-registry-entry-confi) on using "environment variables" with your SSIS project. – Jacob H Sep 05 '19 at 14:56

1 Answers1

1

I solved this issues with the help of this thread: SSIS Connection not found in package

One of the guys gave the hint that you can also deploy a whole SSIS project to SQL Server using the Integration Services Catalog.

In this Microsoft Documentation, everything is explained very well:

Might seem odd that I didn't lookup the doc before I asked the question here in Stackoverflow, but I just couldn't imagine that it is not possible to deploy a single SSIS package when using Project Level connections. A really dumb decision from Microsoft to be honest^^

Yahfoufi
  • 2,220
  • 1
  • 22
  • 41
Walnussbär
  • 567
  • 5
  • 19