blocks|key|1874815|text|好吧，我不喜欢我在那里找到的任何选项。我找到了一些很好的工具来创建脚本，但没有任何工具可以跟踪数据库中的版本并运行新的脚本。无论如何，我继续使用我自己的开源工具来完成这项工作。如果你想使用它，你可以从CodePlex下载它的名字叫KissDB。我还在我的博客blog.RunXc上发布了一篇关于它的博客文章|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1874816|entityMap|0|LINK|mutability|MUTABLE|url|http://kissdb.codeplex.com/|1|http://blog.runxc.com/post/2009/11/18/Announcing-Kiss-Database-Change-Management.aspx^0|37|6|0|3L|A|1|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]|$A|R|B|S|1|T]]|C|$]]|$1|D|3|-4|5|6|7|U|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]]]

OK so I didn't like any of the options that I found out there. I found some good tools to create the scripts but nothing that would track the version in the database and run the new scripts. Anyway I went ahead and rolled my own Open Source tool to get the job done. If you want to use it you can download if from CodePlex its called <a href="http://kissdb.codeplex.com/" rel="nofollow noreferrer">KissDB</a>. I also threw up a blog post about it at my blog <a href="http://blog.runxc.com/post/2009/11/18/Announcing-Kiss-Database-Change-Management.aspx" rel="nofollow noreferrer">blog.RunXc</a>

blocks|key|1874624|text|你看过Open+DBDiff了吗？这可能是一个很好的起点。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1874625|如果您改变了对开源的看法，Red+Gate's+SQL+Compare将是您的首选。|1874626|entityMap|0|LINK|mutability|MUTABLE|url|http://www.codeplex.com/OpenDBiff|1|http://www.red-gate.com/products/SQL_Compare/index.htm^0|3|B|0|0|D|M|1|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]]|C|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]]]

Have you looked at <a href="http://www.codeplex.com/OpenDBiff" rel="noreferrer">Open DBDiff</a> yet? It may be a good place to start.

if you change your mind about open source, <a href="http://www.red-gate.com/products/SQL_Compare/index.htm" rel="noreferrer">Red Gate's SQL Compare</a> is the way to go IMO.

blocks|key|1799637|text|试试dbdeploy.NET|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1799638|http://sourceforge.net/projects/dbdeploy-net/|offset|length|1799639|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|19|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@$D|O|E|P|1|Q]]|A|$]]|$1|F|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|C]]]]

Try dbdeploy.NET

<a href="http://sourceforge.net/projects/dbdeploy-net/" rel="nofollow noreferrer">http://sourceforge.net/projects/dbdeploy-net/</a>

blocks|key|500068|text|在SourceForge上有一个非常有趣的项目叫做SQLRunner+--它是C#，它是.NET，它是过去的"pre-alpha“:-)|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|500069|我自己还没用过，但还是--看起来很不错，IMHO。|500070|Marc|500071|entityMap|0|LINK|mutability|MUTABLE|url|http://sourceforge.net/projects/sqlrunner/^0|P|9|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]]]

There's a pretty interesting project called <a href="http://sourceforge.net/projects/sqlrunner/" rel="nofollow noreferrer">SQLRunner</a> on SourceForge - it's C#, it's .NET, it's past "pre-alpha" :-) 

I've not used it myself, but still - looks quite good, IMHO.

Marc

blocks|key|1801754|text|这是一个棘手的问题，简单明了。其他答案中提到的工具肯定会有所帮助，但您仍然需要自己做很多事情。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1801755|实际上，我的模式中有一个表，其中存储了每个更改脚本的ID+(与我的问题/错误跟踪系统中的案例编号相匹配)。在每个更改脚本的末尾，我将ID插入到该表中。我有一个单独的脚本，用于检查在数据库的任何特定实例上执行了什么操作。自动运行每个尚未运行的脚本是可行的，但我喜欢手动运行更改脚本，以防出现任何错误。|1801756|回滚几乎是不可能的，尤其是在许多模式更改需要某种数据迁移的情况下。我发现，对模式进行任何更改的最佳实践都是使它们向后兼容。永远不要重命名列或表(至少在一开始是这样)。只添加一些东西，并使所有新添加的内容都可以为空。如果你意识到有些地方不太对劲，回滚脚本就会简单地删除新的东西。当然，您最终得到了旧的、未使用的列和表，因此您编写了第二个脚本，该脚本在当前版本被认为是稳定的之后运行，从而消除了旧的东西。|1801757|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

This is a tough problem, plain and simple. The tools mentioned in other answers can definitely help, but you're still left to do a lot yourself.

I actually have a table in my schema that stores an ID for each change script (which matches the case number in my issue/bug tracking system). At the end of each change script I insert the ID into that table. I have a separate script that checks to see what's been done on any specific instance of the database. It would be feasible to automate running each of the scripts that haven't been run yet, but I like to run change scripts manually in case anything goes wrong.

Rollbacks can be almost impossible, especially since many schema changes require some sort of data migration. I have found that best practice with any changes to the schema are to make them backwards-compatible. Never rename a column or table (at least at first). Only add things, and make all new adds nullable. A rollback script simply removes the new stuff, if you realize something isn't quite right. Of course you end up with old, unused columns and tables, so you write a second script that is run after your current release is considered stable, which gets rid of the old stuff.

blocks|key|500088|text|如果你想自己写所有的脚本，你可以利用SQL+Server+2005+TableDiff+Utility，这将给你带来很大的灵活性。一些用法示例可以找到here|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|500089|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/ms162843.aspx|1|http://www.databasejournal.com/features/mssql/article.php/3594926/SQL-Server-2005-TableDiff-Utility.htm^0|I|X|0|23|4|1|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]|$A|R|B|S|1|T]]|C|$]]|$1|D|3|-4|5|6|7|U|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]]]

I you want to write all the scripts yourself you can take advantage of the <a href="http://msdn.microsoft.com/en-us/library/ms162843.aspx" rel="nofollow noreferrer">SQL Server 2005 TableDiff Utility</a> that will give you a lot of flexibility. Some usage examples can be find <a href="http://www.databasejournal.com/features/mssql/article.php/3594926/SQL-Server-2005-TableDiff-Utility.htm" rel="nofollow noreferrer">here</a>

blocks|key|500589|text|如果给定版本的所有脚本都在某个文件夹中，则可以将其作为批处理文件运行(如果将其放在该文件夹中)：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|500590|for+%25%25X+in+(*.SQL)+do+SQLCMD+-S+<SERVER_NAME>+-d+<DATABASE_NAME>+-E+-I+-i+"%25%25X"++>>+ResultBatch.txt|code-block|syntax|javascript|500591|对不起，我不记得我是从哪里弄到这个的，否则我会称赞你的。|500592|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

If you have all of your scripts for a given version in a folder, you can run this as a batch file if you place it in that folder:

<pre><code>for %%X in (*.SQL) do SQLCMD -S &lt;SERVER_NAME&gt; -d &lt;DATABASE_NAME&gt; -E -I -i "%%X" &gt;&gt; ResultBatch.txt
</code></pre>

Sorry, I don't remember where I got this from or I would give credit.

blocks|key|467908|text|我们让开发人员将数据库更改脚本签入Subversion。所有脚本都是可重复的，因此您可以多次运行它们而不会出错。我们还将更改脚本链接到发布项目或bug+if，以便在需要时保留更改集。然后，我们有一个自动化的构建过程，它启动一个单独的SQL脚本文件，并对所有更改进行适当的排序。然后，此单个文件用于将更改发布到测试、QA和生产环境。我们认为这是企业开发人员的最佳方法。更多的细节，我们如何做HERE您的反馈将不胜感激。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|467909|entityMap|0|LINK|mutability|MUTABLE|url|http://www.digitaltools.com/ReleaseManager.aspx^0|5E|4|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]]]]

We have our developers check the database change scripts into Subversion. All scripts are repeatable so you can run them multiple times without error. We also link the change scripts to issue items or bug ids so we can hold back a change set if needed. We then have an automated build process that kicks out a single SQL script file with all of the changes sorted appropriately. This single file is then used to promote the changes to the Test, QA and Production environments. We think this is the best approach with enterprise developers. More details on how we do it <a href="http://www.digitaltools.com/ReleaseManager.aspx" rel="nofollow noreferrer">HERE</a> Your feedback would be appreciated.

blocks|key|467948|text|使用liquibase。不过，它是Java。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|467949|可以，您可以使用您选择的SQL变体编写迁移脚本。|467950|它经过了良好的测试，并被许多人使用。|467951|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Use liquibase. It's Java though.

Yes, you can write your migration scripts in the SQL variant of your choice.

It is well-tested and used by a lot of people.

My need is fairly basic and I don't want to rebuild the wheel. I like to script my database and have written scripts to update it from one version to the next ie 001-create-tables.sql, 002-alter-column.sql etc. 

What I want is a simple tool command line or MsBuild that will look at a database see what version the database is at (using some table convention) and run all of the scripts in a folder that have a higher number than the current database version. I would also like the tool to roll back a script if it fails/throws an error and stop at that point.

That is what I would like but I don't mind changing my conventions though I do want to write my own sql scripts. I also want the tool to be free or open source as I don't need too much.
As my projects are C# I would prefer the tool be built in .Net

Database Change Management using hand generated scripts

33 天实现自己的 AI 进化论？发文瓜分机械键盘、耳机等万元奖池！点击参加活动：<a href="https://cloud.tencent.com/developer/article/2503022" target="_blank">https://cloud.tencent.com/developer/article/2503022</a> 
 <img src="https://qcloudimg.tencent-cloud.cn/raw/01543e0407db10898a7ee9f420794432.jpg"/>

技术创作特训营有奖征文

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

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

腾讯云数据库专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云AI代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

文章&问答评论现已支持表情

我的需求是相当基本的，我不想重建轮子。我喜欢编写我的数据库脚本，并编写脚本将其从一个版本更新到下一个版本，例如001-create-tables.sql、002-alter-column.sql n.sql等。我想要的是一个简单的工具、命令行或MsBuild，它可以查看数据库的版本(使用一些表约定)，并运行文件夹中比当前数据库版本更高的所有脚本。我也希望工具回滚一个脚本，如果它失败/抛出一个错误，

问使用手动生成的脚本进行数据库更改管理
EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用手动生成的脚本进行数据库更改管理EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用手动生成的脚本进行数据库更改管理
EN