SQLServerCentral / Discuss Content Posted by Darren Fuller / Article Discussions / Article Discussions by Author / DB Change Management: An Automated Approach - Part 3 / Latest Posts

RE: DB Change Management: An Automated Approach - Part 3

Darren Fuller — Mon, 16 Aug 2004 07:12:00 GMT

Thanks for the feedback. The approach I have outlined does provide for the change control of "system data" (or "reference data" or "meta data"). It may be just a difference in terminology as I refer to this data in my articles as "static data".

I will reiterate here what has been discussed on the forum for Part 1. I have tried to write the articles as generically as possible. My goal is to convey the concepts of SQL object (and hence database) version control and automated generation of change scripts. My experience of database change management over many years has proven that huge improvements in this area are long overdue. Yes, automation of your processes requires software. But it can be software of your choosing or you can write your own. There are also some good articles around that discuss alternative approaches e.g. links to Steve Jones articles on Part 1 forum.

Thanks,

Darren Fuller

darren.fuller@innovartis.co.uk

RE: DB Change Management: An Automated Approach - Part 3

Clay_G — Mon, 16 Aug 2004 02:17:00 GMT

[q]"make all necessary changes to the target database to ensure that it matches the scripts"[/q]Without the tool, this statement is the whole "ball game".You might as well mention the tool you're flogging by name, and its price.

RE: DB Change Management: An Automated Approach - Part 3

mark baekdal-145375 — Wed, 11 Aug 2004 09:48:00 GMT

Check out www.dbghost.com - it is the tool as talked about in Darrens article.

RE: DB Change Management: An Automated Approach - Part 3

hurcane — Wed, 11 Aug 2004 08:00:00 GMT

I'm with you 100% on the need for an automated method to change management. I agree with you completely on how the automated process should work.The key to making all of this work is described as the "change control tool". The problem I have is that I haven't been able to find a comprehensive change control tool that does all the things that are described in the article.One point that is missing on the change control tool is "system data". Schema is referenced frequently, but most databases also have tables that control certain aspects of the application. This system data would also need to be kept under source control and handled automatically by the vaporous change control tool.If somebody can recommend a change control tool that does all these things and is affordable for a team of less than 10 people, I'm all ears!

DB Change Management: An Automated Approach - Part 3

Darren Fuller — Fri, 23 Jul 2004 16:02:00 GMT

Comments posted to this topic are about the content posted at http://www.sqlservercentral.com/