GIT上的SSIS解决方案? [英] SSIS solution on GIT?

问题描述

我找不到有关与SSIS解决方案一起使用的版本控制的大量资源.将SSIS解决方案放在GIT存储库上是适当"的事情，还是这种类型的项目还有其他(更好)的解决方案.我对git很熟悉，但是我不确定它如何与SSIS一起使用，因为这主要是UI方面的问题，我不知道是否可以将git弄乱，是否有任何需要注意的地方，等等.

I can't find much resources about what version control to use with SSIS solution. Is it "proper" thing to do to put SSIS solution on GIT repository or there are other (better) solutions for this type of projects. I am familiar with git but I am not sure how would it work with SSIS since it's mostly UI thing I don't know if putting on git can mess up anything, are there any things to be careful with, etc.

推荐答案

相反，SSIS的接口通常是通过UI，但从本质上讲，它是大量的XML.

Au contraire, the interface to SSIS is generally through a UI but at the heart it's an ungodly amount of XML.

是的，您可以并且应该对SSIS解决方案进行版本控制，就像应该对开发的任何内容进行版本控制一样.不管是纯" XML还是从SSIS中获得的东西，合并XML都是最好的选择:描述工作流和的XML，嵌入其中的XML是描述GUI元素布局的更多XML.合并SSIS包时，布局和工作的混合会导致很多冲突.像 BIDS Helper 这样的工具会尝试提供智能差异".我发现识别此数据流已更改"对我很有帮助，但否则，我将SSIS包视为源代码控制中的二进制对象.

So yes, you can and should version control your SSIS solutions, as you should version control anything you develop. Merging XML is dicey at best, whether it's "straight" XML or what we get with SSIS: XML that describes the workflow and, embedded in that XML is more XML that describes the layout of GUI elements. That mix of layout and work leads to a lot of conflicts when merging SSIS packages. There are tools like BIDS Helper that attempt to provide a "smart diff". I find that it's helpful for me to identify "this data flow changed" but otherwise, I treat SSIS packages as binary objects in source control.

无论您使用git，mercurial，svn，csv，rcs，perforce，tfs，sourcesafe还是任何其他工具，对于要版本化的内容类型都是100％不重要的.

Whether you use git, mercurial, svn, csv, rcs, perforce, tfs, sourcesafe or any other tool is 100% immaterial to the type of content being versioned.

这篇关于GIT上的SSIS解决方案?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！