SSIS solution on GIT?

Question

I cannot find many resources about which version control to use with SSIS. Is it right to do this to put the SSIS solution in the GIT repository or are there other (better) solutions for this type of project. I am familiar with GIT, but I am not sure how this will work with SSIS, since it is basically a user interface that I don’t know if putting on GIT can ruin something, are there any things to be careful with etc.

Answer 1

Au contraire, the interface for SSIS, is usually provided through the user interface, but it is based on a fuzzy amount of XML.

So, you can and should control the versions of your SSIS solutions, since you must control the version you are developing. XML merging is risky at best, whether it’s "direct" XML or what we get with SSIS: XML describing the workflow and embedded in this XML is more XML that describes the layout of GUI elements. This combination of layout and operation leads to many conflicts when bundling SSIS packages. There are tools like BIDS Helper that try to provide smart diff. I find it helpful to identify “this data stream has changed,” but otherwise I see SSIS packets as binary objects in source control.

Whether you use git, mercurial, svn, csv, rcs, perforce, tfs, sourcesafe or any other tool are 100% irrelevant for the type of version whose version it is.