使用 SSAS、TFS 和 SSAS 管理团队发展投标报价系统
我目前是公司数据仓库和多维数据集的一名 BI 开发人员。我使用 SQL Server 2008、SSAS 和 SSIS 作为我的基本工具包。我使用 Visual Studio +BIDS 和 TFS 作为我的 IDE 和源代码控制。我即将与离岸供应商一起承担多个项目，我担心管理变革。我主要关心的是管理我和离岸团队之间的合并和变更。合并和管理对 SQL 和 SQL 的更改XML 对于一个人来说已经够糟糕了，但是对于多个开发人员来说，这似乎是一场噩梦。知道有时无法避免多个人对同一文件进行更改，对于如何最好地构建开发有什么想法吗？
I am currently a single BI developer over a corporate datawarehouse and cube. I use SQL Server 2008, SSAS, and SSIS as my basic toolkit. I use Visual Studio +BIDS and TFS for my IDE and source control. I am about to take on multiple projects with an offshore vendor and I am worried about managing change. My major concern is manging merges and changes between me and the offshore team. Merging and managing changes to SQL & XML for just one person is bad enough but with multiple developers it seems like a nightmare. Any thoughts on how best to structure development knowing that sometimes there is no way to avoid multiple individuals making changes to the same file?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
SSIS、SSAS 和 SSRS 文件不适合合并。它们存储在一个 xml 文件中，该文件发生了巨大的变化 - 即使有微小的变化（例如更改属性） - 因此它实际上变得不可能合并。
因此，不要再考虑在一个文件上进行并行开发。您需要考虑如何实现人们不需要在一个文件上进行并行开发。因此，首先要禁用文件的多重检出。您甚至可能需要考虑启用在结账时获取最新版本的选项。
然后开始思考如何实现人们能够独立工作。这更多的是你构建工作和文件的方式：
我已经向产品团队反馈了 BIDS 不兼容合并的情况。这是一个已知问题，但很难解决。他们不知道什么时候才能真正对这些文件进行并行开发。在此之前，请远离并行开发。
SSIS, SSAS and SSRS files are not merge-friendly. They are stored in an xml file that is changed drastically - even with minor changes (such as changing a property) - so it becomes really impossible to merge.
So stop thinking about parallel development on one file. You need to think how you can achieve that people are not need to do parallel development on one file. So start with disabling the multiple checkout of a file. You might even want to consider to enable the option to get the latest version on a checkout.
Then start thinking how you can achieve that people can work independent. This is more in the way you structure the work and files:
I have given feedback to the product team of the imcompatability of BIDS to merge. It is a known issue, but will be hard to tackle. They don't know when it will be possible to really do parallel development on these files. Until then keep away from parallel development.
正如 Ewald Hofman 提到的，SSAS 和 SSIS 不适合合并。
在一种环境中，我解决了如下问题：
构建一个 C# 应用程序，通过 AMO API（我知道，一开始这是一项艰巨的工作，但它是值得的 - 想想你会得到什么 - 看看下面的优点）
添加阶段数据库并将 C# 应用程序添加到您的存储库（TFS/Git 等）
该结构的优点：
缺点：
结论：
As Ewald Hofman mentioned, SSAS and SSIS is not merge-friendly.
In one environment I worked solved the problem as follows:
build a C# application that build your dimensions and cubes via the AMO API (I know, that's a tough job at the beginning but it is it worth - think on what you gain - Look at the Pros below )
add the stage database and the C# application to your Repository (TFS/Git etc.)
Pros of that structure:
Cons:
Conclusion:
http://code.google.com/p/support/wiki/DVCSAnalysis
也许更好的标签是 DVCS？
https://stackoverflow.com/questions/tagged/dvcs
http://code.google.com/p/support/wiki/DVCSAnalysis
maybe a better tag is DVCS?
https://stackoverflow.com/questions/tagged/dvcs
只要两个团队都使用出价和 TFS，这就不成问题。
假设您的 tsql 代码在每个对象的单个文件中签入源代码管理，合并 TSQL 代码是直接的，因为它是基于文本的。我发现 VSTS 数据库项目对此有帮助。
合并 SSIS 和 MSAS 的基于 XML 的源文件可能会很麻烦，如下所示。为了减轻一些痛苦，我发现将每个包限制为单个数据流或逻辑工作单元有助于减少开发人员对包的争用。然后，我从一个或多个主包中调用这些包。我还尝试使用存储过程、视图或 udfs 将所有 tsql 源查询外部化，以便进一步减少编辑包的需要。使用配置文件和变量在较小程度上也有帮助。
MSSAS 立方体稍微坚硬一些。我最好的建议是研究第 3 方 xml 差异工具。我已经能够使用基于标准文本的工具成功合并小的更改，但这可能是一项艰巨的任务。
As long as both teams are using bids and TFS this should not be a problem.
assuming that your tsql code is checked in to source control in a single file per object, merging TSQL code is straight forward since it is text based. I have found the VSTS Database projects help with this.
Merging the XML based source files of SSIS and the MSAS can be cumbersome as you indicate below. to alleviate some of the pain, I find that keeping each package limited to a single dataflow or logical unit of work helps reduce developer contention on packages. I then call these packages from one or more master packages. I also try to externalize all of my tsql source queries using sprocs, view or udfs so that the need to edit the package is further reduced. using configuration files and variables also helps to a smaller extent.
MSSAS cubes are a little bit tougher. My best suggestion is to look into a 3rd party xml differencing tool. I have been able to successfully merge small changes use the standard text based tools but it can be a daunting task.