Change "ALL" Packages in a Project to use Project Configuration Table

Question

We have numerous SSIS PROJECTS where all of the packages that were developed use local connection managers.  We now want to use a configuration file in SQL Server to contain the connection information.  When I right click on the project, the Option
that I'm provided is to "Convert to Package Deployment Model".  When I right click on the Control Flow and select Configurations, the "Package Configurations Organizer" dialog opend and the "Enable package configurations"
check box is not checked.  We have over 300 packages like this and I'm hoping that someone knows of a procedure to have the entries specified in the "Package Configuration Organizer" apply to all packages in the project.
Please let me know.
Thank you
Bigguy

Answer 1

Is there a painless way to transition the local connection to the project connection without having to manually address each task that becomes invalidated?
Hi BigGuy,
I am afraid the answer is no.
After we convert a connection manger in a package to a project connection manager, the connection manager will be added to each package within the project. If a package already includes a connection manager with the same name as the project connection manager,
the project connection manager will not be visible until we delete the existing package connection manager that has the same name. After we delete the package connection manager, it’s true that the tasks that uses the package connection manager will become
invalid with the following error message:
Error at Package1: The connection "{XXXXX}" is not found. This error is thrown by Connections collection when the specific connection element is not found.
That’s because a SSIS task refers to a connection manager based on the GUID of the connection manager, however, the GUID become invalid once we delete the package connection manager. To address this issue, we have to manually open each task that throws errors
to update the task. However, it should not be very painful because we can double click to open the task editor, and then just click “OK” to close the window. In this way, the task will be updated with the project connection manager automatically.
Regards,
Mike Yin
If you have any feedback on our support, please click here
Mike Yin
TechNet Community Support