Hi, We are using SSIS 2014 and have Project parameters & connection managers. In this ETL solution we have packages that use most of the project connection managers. But, there are also a few SSIS packages which do not use all these connection managers. In that I want only those connection managers related to that specific package. If I delete a project connection manager from a package it deletes it altogether from the project itself. What's the work around for this?

For instance: There's ProjConnMgr1, ProjConnMgr2, ProjConnMgr3. I have 5 different SSIS packages and all use ProjConnMgr1 and only 3 use ProjConnMgr2 & 2 use ProjConnMgr3. So, in the 3 SSIS packages in the Connection Manager we just want to see ProjConnMgr1, ProjConnMgr2 and the remaining 2 ProjConnMgr1, ProjConnMgr3.

Hope this expalins....

Thanks in advance

Hi Ione,

thank you for coming back here,

You can demote the project connection to become package-wise in scope by right-clicking it

I am not sure if this is possible.  If you have a project level connection, it will always show in the connection manager for every package part of that project.  If you convert the connection to a package connection, each package dependent on the project connection will no longer have access to it.  Instead, you will need to manually configure each connection per package.

However, it would be a nice to have feature in the Connection Manager to only show used connections within the package.  The only other way to clean up the connection manager is to basically create a new project with only the shared project connections that you need.  Unlike Visual Studio projects, SSIS environment variables are shared across all the projects in the same folder.  This will allow you to have multiple projects use the same environment variable definition even if the projects do not use all the variables defined.

Hi Ione,

After creating a project level connection manager in the project, it will also appear in the Connection Managers tab in the SSIS Designer window for all the packages in the project. The name of the connection manager in this tab will have a (project) prefix in order to differentiate this project level connection manager from the package level connection managers. There is no way to hide the unused project level connection manager in a package.

Besides, once a project connection manager gets demoted all other packages that use this project connection will have their reference broken. So this option also cannot achieve your requirement.

If you have concern about this feature, it is my pleasure to help you to reflect your recommendation to the proper department for their consideration. Please feel free to submit your situation on our product to the following link https://connect.microsoft.com/SQLServer/. Your feedback is valuable for us to improve our products and increase the level of service provided.

Thanks,
Katherine Xiong