SSIS Connection Managers Should be Referenced by Name not just by GUID - by Joe Salvatore

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 484122 Comments
Status Closed Workarounds
Type Bug Repros 3
Opened 8/20/2009 7:34:51 AM
Access Restriction Public


SSIS objects that use connection managers do so by the connection manager object GUID and not the name of the connection manager.
As a result when BIDS Helper's Reset GUIDs (or any other means of changing the connection manager's GUID value) is used object references are "specifically" coded to reference that package's connection manager.
For development productivity, if you subsequently copy and paste any SSIS object from one package to another after having previously setup connection managers using uniform names, all the pasted objects that contain references to these connection managers will produce an error "Connection manger {your GUID} does not exist. When opening an object with the error "Connection manger {your GUID} does not exist you will note that the Connection property value has a GUID rather than a named connection manager value.

Additionally, should you use SSIS variable's with property expressions to store your SQL, you will note that the varaible with the same name has no problem being referenced after performing the reset GUID.

The expected behavior in the scenario outlined would be that of all other SSIS objects, that is match based on object name not based on GUID.
Sign in to post a comment.
Posted by Microsoft on 8/30/2010 at 5:02 PM
Thank you for contacting us. After analyzing this issue and prioritizing it in the context of our current development plans, we have found regretfully that it does not meet the bar to be included in an upcoming product release. If you feel that you could provide us with more data to change that judgment, we welcome any further information. Your feedback continues to be invaluable to us and we take all your communication seriously. Please continue to contact us with any questions, suggestions and issues as they arise.

     The SSIS Team
Posted by Microsoft on 8/27/2009 at 9:37 AM
Thank you for your submission. We will be reviewing your information and providing you feedback on our findings and progress. Thanks for your interest and support of SSIS.