使用索引进行变更管理的最佳实践

我们的IT商店首先开始建立一组DBA.我们所有人(包括我自己)都来自应用程序开发/架构世界,因此DBA世界对我们来说仍然是一个新手.

除了构建DBA组之外,我们还希望在需要移动更改时构建变更管理过程和流程(希望基于最佳实践).

我发现following post对主要是触发器,存储过程和/或DDL更改很有帮助.但它不一定能解决索引或供应商数据库问题.

我们混合使用自己的数据库和供应商数据库.在我们的案例中,一些供应商(尽管不是全部)正在与我们公司合作构建数据库和应用程序.我们正在对应用程序进行性能测试,然后才能“上线”.因此,我们正在大量分析指数(或缺乏指数).

当我们遇到我们认为应该制作的索引时,对于我们自己的数据库以及任何供应商,我们如何最好地处理有关这些的变更管理?

你在店里做什么?我对这个过程的工具很少担心.

EDIT: So far, I’m appreciating the feedback, comments, and answers for this question. I have noticed that some of the answers are a bit
tool specific. I’m looking for more “agnostic” practices, if that can
be had.

However if agnostic is not possible, then for tool sets, we use IBM
DB2 LUW (and that actually on AIX) mostly. We have some DB2 on Windows
and DB2 for i (IBM’s i5/OS), but we are mostly AIX DB2. We do use
source control, specifically Subversion.

Again, looking for general best practices, but above is what we use
that would be vendor specific.

EDIT:
Current Decision: We intend to track our reasoning as well as our changes. So we are going to open an issue in our issue-tracking
software (which in our case is JIRA). Now we can add in documentation
as to what priority the change has, data that backs up what the change
should be, the change, and the results of the change from another
environment where the change was tested.

We then also intend to keep track of our changes in scripts in SVN
(much like was suggested below). This way we can track what version of
what exists where. This can be recorded in our JIRA issue (and in any
other auditing software we use, ie. pasted links). We can know with
more certainty what change went to what environment and why. We can
then also track if the index was something we added beyond the vendors
implementation or ahead of their implementation, etc.)

最佳答案
我强烈建议您对数据库的处理方式与处理应用程序代码的方式基本相同.您可以将数据库编写到其组件部分,并将其检入源代码控制,然后使用相同的标签和放大器.您用于应用程序的版本.

要使对象进入源代码管理,您可以使用许多工具.微软有一个绰号为Data Dude的工具.它适用于Visual Studio.他们还准备发布一个名为SQL Server数据库工具(SSDT)的新工具,再次使用Visual Studio.我的公司Red Gate Software制作了一个与SSMS一起使用的工具,称为SQL Source Control.

在过程方面,我为Red Gate Guide to Team Development书写了几个章节.它可以免费下载(或者如果你想杀死一棵树,你可以从亚马逊那里获得一个).我将详细介绍如何在那里开发团队中使用数据库.

转载注明原文:使用索引进行变更管理的最佳实践 - 代码日志