blocks|key|4222529|text|是的，看看Red+Gate的SQL+Source+Control就有一个选择|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4222530|entityMap|0|LINK|mutability|MUTABLE|url|http://www.red-gate.com/products/sql-development/sql-source-control/^0|E|I|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Yep, check out Red Gate's <a href="http://www.red-gate.com/products/sql-development/sql-source-control/" rel="nofollow">SQL Source Control</a> for one option

blocks|key|1906040|text|在IDE中，可以从Red+Gate使用SQL源代码管理|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1906041|否则，您可以将对象编写为source-controlled+folder脚本。为此，我们使用Red+Gate+(因为在SQL源代码控制发布之前)|offset|length|1906042|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/1586697/exposing-sql-server-database-objects-as-files-in-a-file-system/1597085#1597085^0|0|C|O|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

In the IDE you can use SQL Source Control from Red Gate

Otherwise, you can script your objects into <a href="https://stackoverflow.com/questions/1586697/exposing-sql-server-database-objects-as-files-in-a-file-system/1597085#1597085">source-controlled folder</a>. We use Red Gate for this (since before SQL Source Control was released)

blocks|key|1554893|text|为此，我喜欢将代码与数据分开。因此，视图、StoredProcs、函数像普通一样得到版本控制，但对表、索引、数据的更改被存储为增量更改。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1554894|如果您有足够的预算，System和RedGate+VS2010+Source+Control都是不错的选择。|1554895|也就是说，创建自己的应用程序并不太难。您将需要两个组件：|1554896|1554897|将所有代码对象从DB拉到磁盘的脚本|ordered-list-item|1554898|将代码对象从磁盘部署到DB|1554899|的脚本|1554900|我在https://github.com/ScottWeinstein/PSIS上有一些关于如何做到这一点的示例|offset|length|1554901|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/ScottWeinstein/PSIS^0|0|0|0|0|0|0|0|2|12|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|10|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|11|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|12|8|@]|9|@]|A|$]]|$1|G|3|H|5|I|7|13|8|@]|9|@]|A|$]]|$1|J|3|K|5|I|7|14|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|15|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|16|8|@]|9|@$P|17|Q|18|1|19]]|A|$]]|$1|R|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|S|$T|$5|U|V|W|A|$X|Y]]]]

I like to separate code from data for this purpose. So Views, StoredProcs, Functions get version controlled like normal, but changes to tables, indices, data, are stored as incremental changes.

If you have the budget, VS2010 Team System is a nice option, as is RedGate Sql Source Control.

That said, it's not too hard to roll your own. You'll need two components:

<ol>
<li>A script to pull all code objects from the DB to disk</li>
<li>A script to deploy the code objects from disk to DB</li>
</ol>

I've some samples on how to do this at <a href="https://github.com/ScottWeinstein/PSIS" rel="nofollow">https://github.com/ScottWeinstein/PSIS</a>

blocks|key|5691045|text|我有一个开源(在LGPL许可下)的工具集项目，它试图解决与正确的DB+schema版本控制(以及更多)相关的问题，即bsn+ModuleStore。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|5691046|基本上，它的独立部分将数据库模式的SQL+Server+DB对象编写为应用了标准格式的文件，因此只有当对象确实发生更改时，文件内容才会更改(这与VS执行的脚本非常不同，后者还会将某些脚本日期等脚本标记为已更改，即使它们实际上是相同的)。|5691047|但是如果您使用.NET，那么这个工具集就超出了这个范围:它允许您将SQL脚本嵌入到库或应用程序中(作为嵌入式资源)，然后让它将嵌入的脚本与数据库中的当前状态进行比较。与表无关的更改(根据Martin+Fowler's+definition，这些更改不是“破坏性更改”)可以自动应用，也可以根据请求应用(例如，创建和删除对象，如视图、函数、存储过程、类型、索引)，并且更改脚本(需要手动编写)也可以在相同的过程中应用；还可以创建新的表，可选地与它们的设置数据一起创建。更新之后，将再次将DB模式与脚本进行比较，以确保在提交更改之前成功升级DB。|5691048|根据您希望访问数据库的方式，提供的工具集可以做得更多-它实现了一些.NET功能，并提供了一种非常好用的基于接口的方法来调用存储过程，包括使用原生XML类透明地支持.NET，以及像IEnumerable<PocoClass>一样支持TVP(表值参数)。|style|CODE|5691049|entityMap|0|LINK|mutability|MUTABLE|url|http://code.google.com/p/bsn-modulestore/|1|http://martinfowler.com/articles/evodb.html^0|1M|F|0|0|0|2L|Q|1|0|2H|M|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@$A|W|B|X|1|Y]]|C|$]]|$1|D|3|E|5|6|7|Z|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|10|8|@]|9|@$A|11|B|12|1|13]]|C|$]]|$1|H|3|I|5|6|7|14|8|@$A|15|B|16|J|K]]|9|@]|C|$]]|$1|L|3|-4|5|6|7|17|8|@]|9|@]|C|$]]]|M|$N|$5|O|P|Q|C|$R|S]]|T|$5|O|P|Q|C|$R|U]]]]

I have an open-source (licensed under LGPL) toolset project which tries to address the issues related to proper DB schema versioning (and more), the <a href="http://code.google.com/p/bsn-modulestore/" rel="nofollow">bsn ModuleStore</a>.

Basically, the standalone part of it scripts the SQL Server DB objects of a DB schema into files with a standard formatting applied, so that the file contents only changes if the object really did change (very much in contrast to the scripting done by VS, which scripts some scripting date etc. as well, marking all objects as changed even if they are in fact identical).

But the toolset goes beyond that if you use .NET: it allows you to embed the SQL scripts into the library or application (as embedded resources) and then have it compare the embedded scripts with the current state in the database. Non-table-related changes (those that are not "destructive changes" as per <a href="http://martinfowler.com/articles/evodb.html" rel="nofollow">Martin Fowler's definition</a>) can be applied automatically or on request (e.g. creating and removing objects such as views, functions, stored procedures, types, indexes), and change scripts (which need to be written manually though) can be applied in the same process as well; new tables are also created, optionally along with their setup data. After the update, the DB schema is again compared against the scripts in order to ensure a successful DB upgrade before the changes are committed.

Depending on how you want to access the database, the toolset offers does even more - it implements some ORM capabilities and offers a very nice and useful interface-based approach to invoke stored procedures, including transparent support for XML with native .NET XML classes and also for TVPs (Table-Valued Parameters) as <code>IEnumerable&lt;PocoClass&gt;</code>.

Are there any tools/techniques available for Integrating SQL Code with Subversion for versioning?

Are there any tools/techniques available for Integrating SQL Code with Subversion for versioning?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

是否有任何工具/技术可用于将SQL代码与Subversion集成以进行版本控制？

问是否有任何工具/技术可用于将SQL代码与Subversion集成以进行版本控制？
EN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问是否有任何工具/技术可用于将SQL代码与Subversion集成以进行版本控制？EN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问是否有任何工具/技术可用于将SQL代码与Subversion集成以进行版本控制？
EN