Home Dashboard Directory Help

BIDS/SSDT shouldn't save any package-specific information in the project file (.dtproj) by Andrej Kuklin



Sign in
to vote
Type: Suggestion
ID: 753579
Opened: 7/13/2012 4:22:53 AM
Access Restriction: Public


Currently BIDS/SSDT saves a bunch of package metadata in the project file:

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
Sign in to post a comment.
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.
Sign in to post a workaround.