October 25, 2017 at 11:05 am
We are collaboratively developing SSIS packages in Visual Studio Community Edition 2015.
What is the best source control product that would allow collboration of changes on working on different SSIS packages?
October 25, 2017 at 11:12 am
chris.asaipillai-624309 - Wednesday, October 25, 2017 11:05 AMWe are collaboratively developing SSIS packages in Visual Studio Community Edition 2015.What is the best source control product that would allow collboration of changes on working on different SSIS packages?
Any of the main VCS tools will do the job. Current flavour of the month is probably Git.
Note that it is practically impossible for two developers to work on changes to the same SSIS package & then merge those changes, regardless of VCS.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
October 25, 2017 at 12:48 pm
We use VSTS (Visual Studio Team Services) which allows use of GIT or TFS.
As Phil says - two developers working on the same package and trying to merge changes equals a nightmare. We have an internal rule that it is up to the person to check no one else has a package checked out before checking it out and trying to work on it.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply