blocks|key|901518|text|在敏捷数据库开发方面，AgileData.org是一个很好的资源--比我在单个响应中塞进的资源多得多。特别是，您可能对Agile+Data+Best+Practices感兴趣。如果您使用SQL+Server，您可能还会对Red+Gate软件的SQL+Compare感兴趣。我们的DBA使用它来帮助我将现有应用程序的更改从QA迁移到生产环境。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|901519|entityMap|0|LINK|mutability|MUTABLE|url|http://www.agiledata.org/|1|http://www.agiledata.org/essays/bestPractices.html|2|http://www.red-gate.com/index3.htm^0|B|D|0|1N|P|1|32|8|2|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]|$A|T|B|U|1|V]|$A|W|B|X|1|Y]]|C|$]]|$1|D|3|-4|5|6|7|Z|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]|N|$5|G|H|I|C|$J|O]]]]

<a href="http://www.agiledata.org/" rel="noreferrer">AgileData.org</a> is an excellent resource -- much more than I cram into a single response -- on Agile Database development. In particular, you might be interested in <a href="http://www.agiledata.org/essays/bestPractices.html" rel="noreferrer">Agile Data Best Practices</a>. If you use SQL Server, you might also be interested in SQL Compare from <a href="http://www.red-gate.com/index3.htm" rel="noreferrer">Red Gate</a> software. Our DBAs have used it to help me migrate changes from QA to Production for existing applications.

blocks|key|76539|text|对于每一次更新，我会：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|76540|76541|部署前滚和回滚脚本，|unordered-list-item|76542|部署“从头开始构建数据库”脚本，|76543|部署数据迁移脚本，以及|76544|实施将代码锁定到数据库版本的机制，即测试返回数据库的当前版本的值，如果存在不匹配，系统将退出并大声抱怨不匹配。|76545|<+code+>F29|76546|HTH|76547|干杯,|76548|抢夺|76549|entityMap^0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|W|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|X|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|Y|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|Z|8|@]|9|@]|A|$]]|$1|J|3|K|5|E|7|10|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|11|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|12|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|13|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|14|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|U|$]]

For each update, I'd be:

<ul>
<li>deploying roll forward and rollback scripts,</li>
<li>deploying a "build the DB from scratch" script,</li>
<li>deploying a data migration script, and</li>
<li>enforcing a mechanism whereby the code is locked to the database version, i.e. testing for a value that returns the current version of the DB, if there's a mismatch, the system bails and bleats loudly about the mismatch.</li>
</ul>

HTH

cheers,

Rob

blocks|key|906796|text|在我们的敏捷设置中，有一个用于DB更改的文件夹，以.SQL文件的形式完成。到目前为止，我们在每个版本中都有一个DB更改，该文件以应用程序版本命名。安装脚本在更新站点时自动应用所有更改文件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|906797|我们还有一个完整的模式转储的参考数据库，用于新的安装，由我们的数据库管理工具创建。|906798|我知道有一些工具可以帮助自动化这个过程，比如Red+Gate，但是手动创建SQL更改文件非常简单。|906799|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|$]]

In our Agile setup, there's a folder for DB changes, done as .SQL files. So far we've had a DB change in every version, and the file is named after the app version. The install script automagically applies all the change files when updating sites.

We also have a full schema dump of a reference DB, that's used for new installs, created by our DB Admin tool.

I know there are tools that help automate this process, such as Red Gate, but manually creating the SQL change file is very easy.

blocks|key|4142971|text|理想情况下，您可以进行非破坏性的更改，然后在发布完成后，您可以完全弃用模式的旧部分。这并不容易，而且需要纪律。这并不总是可能的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4142972|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Ideally you make non breaking changes, then when release is done you can fully deprecate old parts of the schema. This is not easy and requires discipline. It is not even always possible.

blocks|key|906768|text|看看Ruby+on+rails+migrations吧。如果你不使用Rails也没关系，因为这个想法已经被复制到其他框架中了。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|906769|entityMap|0|LINK|mutability|MUTABLE|url|http://wiki.rubyonrails.org/rails/pages/understandingmigrations^0|2|O|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]]]]

Take a look at <a href="http://wiki.rubyonrails.org/rails/pages/understandingmigrations" rel="nofollow noreferrer">Ruby on rails migrations</a>. Doesn't matter if you don't use Rails, as the idea has been copied to other framework already.

blocks|key|76588|text|数据库结构很可能依赖于代码的许多部分，模式更改将产生级联效应。这有点像对一个类中的接口进行更改，其中包含了许多类的扩展。因此，对于模式更改要小心。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|76589|敏捷方法论与其他方法论没有什么不同，因为尽可能提前设计数据库对您有好处，并且您应该寻求比代码更少的更改频率。这并不是说你永远不能改变它，但这样做的代价是高昂的。|76590|正如其他人所指出的，迁移是一种简单但有效的跟踪模式更改的工具。这个概念是CREATE和ALTER语句的脚本，用于从模式的一个修订版升级到下一个修订版，伴随着ALTER和DROP语句的脚本，用于将相同的更改降级。Ruby+on+Rails在此基础上使用了一个数据库抽象层，以使切换数据库品牌变得更容易，但如果您只需要支持一种品牌，则可以简单地使用SQL文件。|76591|关于这个主题，有一本备受好评的书(尽管我还没有花时间去买或读它)，书名叫"Refactoring+Databases:+Evolutionary+Database+Design“，作者是Scott+Ambler|offset|length|76592|entityMap|0|LINK|mutability|MUTABLE|url|https://rads.stackoverflow.com/amzn/click/com/0321293533^0|0|0|0|11|1F|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@$H|V|I|W|1|X]]|A|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

The database structure is most likely to be a dependency of many parts of your code, and schema changes will have cascading effects. Kind of like making changes to the interface in a class which many classes extend. So be cautious about schema changes.

Agile methodology is no different than other methodologies in that it's to your benefit to design the database up front as much as possible, and you should seek to change it less frequently than the code. Not to say you can never change it, but it is costly to do so.

Migrations are a simple but effective tool for tracking schema changes, as others have noted. The concept being scripts of CREATE and ALTER statements to upgrade from one revision of the schema to the next, accompanied by scripts of ALTER and DROP statements to downgrade the same changes. Ruby on Rails uses a database abstraction layer on top of this to make it easier to switch brands of database, but if you only need to support one brand you could simply use SQL files.

There's a highly-regarded book on this subject (though I haven't gotten around to buying or reading it yet) called "<a href="https://rads.stackoverflow.com/amzn/click/com/0321293533" rel="nofollow noreferrer" rel="nofollow noreferrer">Refactoring Databases: Evolutionary Database Design</a>" by Scott Ambler

For those agile practitioners out there...

How do you manage changes to a database schema during a project? My assumption is that in an agile project the schema of any database involved will change and be refactored just as happens with the codebase.

Is this assumption correct? If so, do you have any particular tools or processes that you use to help keep things running smoothly?

Agile development and database changes

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

对于那些敏捷实践者来说...如何在项目期间管理对数据库架构的更改？我的假设是，在敏捷项目中，涉及到的任何数据库的模式都会发生变化并被重构，就像代码库一样。这个假设是正确的吗？如果是这样的话，您是否有任何特定的工具或流程可以帮助保持顺利运行？

问敏捷开发和数据库变更
EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问敏捷开发和数据库变更EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问敏捷开发和数据库变更
EN