Status :

Description

Currently BIDS/SSDT saves a bunch of package metadata in the project file:
-ID
-Versions
-Descriptions
-Parameters(!!!)
which means a great trouble when more than 1 developer works on the SSIS project.
Imagine following typical situation:
1. Developer1 checks out and starts working on an existing package1 => version information is updated in the .dtproj file
2. Developer2 checks out and starts working on an existing package2 => version information is updated in the .dtproj file. He adds, for instance, a new parameter to the package2
3. Developer2 checks in his changes + the changed .dtproj file
4. Developer1 now has the "pleasure" to merge his changes in the .dtproj file with the check in of Developer2 before Developer1 can actually check in his work

Assign To

"The fix is risky to implement in the current version of the product" and therefore "we will not fix in the current or _future_ versions of SSIS"?

Logic I can't understand

Posted by Microsoft on 3/19/2015 at 11:09 PM

Thank you for submitting this feedback. After carefully evaluating all of the bugs in our pipeline, we are closing bugs that we will not fix in the current or future versions of SSIS. The reasons for closing these bugs are following:- The fix is risky to implement in the current version of the product

If the issue is a critical business interruption, please call CSS (Customer Support Services).Thanks again for reporting the product issue and continued support in improving our product. We will continue to improve developer experience in the future.

Posted by Hubert K on 10/29/2014 at 7:58 AM

I absolutely agree. Merging project files is nightmare with all those package-specific elements. Keep them in package files and we will be much better in team SSIS packages developemnt.

Posted by Simon Givoni _ on 3/5/2014 at 6:00 AM

Now today I expierenced the exact same thing when changing properties in the flat file connection in the package! The project file had to be updated! But why?

To ague that one need to use version control but not beeing able to easily use it with more than one developer is actually a setback compared to SSIS2008.

Posted by Jamie Thomson on 10/24/2012 at 9:15 AM

Completely agree. Its crazy that this goes on - I have experienced the same issues as Utwigg.

Posted by Microsoft on 8/27/2012 at 9:07 PM

Thank you for your feedback. We are actively looking at the issue and will keep you updated.