Versioning in a large SSIS ETL project

Question

Versioning in a large SSIS ETL project

We are going to convert data from one system to another using SSIS. We are four people who will work on this for two years, and therefore we need some kind of version control system. We cannot use the foundation of the team. We are currently setting up an SVN server, but we delve into it, I saw some big risks.

It seems that the solution is stored in one huge XML file. This should be a huge problem in a combined code drag and drop environment like SSIS, since SVN will not be able to merge the changes correctly, and whenever we get an error while committing, we will have to look inside this huge XML file and fix the errors manually.

One way to solve this problem is to create many solution projects in SSIS. However, this is not the setting that we want, because we are creating one big monster that will have 2 days to complete, and we want to monitor its progress as it progresses. If we need to create several solutions, are there any ways to relate their execution and still have a visual appearance of what is happening and how well is the execution performed?

Has anyone had similar problems and / or do you have any suggestions on how to solve them?

+3

version-control ssis

Per stilling Mar 31 '10 at 9:33

source share

3 answers

? , , ? , , , , :