Comments on: Gradual deployment of schema changes

By: Best practices for schema changes and data migrations to a live database without downtime? | web technical support

Wed, 18 Jan 2012 23:19:12 +0000

[...] article deals with the problem http://nothing.tmtm.com/2009/02/gradual-deployment-of-schema-changes/ but I didn’t really understand step 3. He says to write to both tables, then migrate old data [...]

By: What are some strategies for continuous deployment when database schemas are changing? - Quora

Mon, 24 Jan 2011 23:30:22 +0000

[...] Schmidt, CTO @ netguru, http://blog.netguru.pl Here is a great writeup on this:http://nothing.tmtm.com/2009/02/…Insert a dynamic date hereView All 0 CommentsCannot add comment at this [...]

By: Chris

Chris — Thu, 04 Feb 2010 22:48:12 +0000

There’s a tool called ChronicDB that tries to address this problem of “before” and “after” versions of client applications.

By: Aristotle Pagaltzis

Aristotle Pagaltzis — Wed, 01 Apr 2009 04:44:19 +0000

Someone recently posited that a database archaeologist could tell the age of a system by how many 1-1 relationships still existed. I can’t remember who or where

You mean Rules of Database App Aging. And actually, he says that it’s not remaining 1-to-1 relationships that he gauges age by, but remaining NOT NULL constraints.

By: Timothy Fitz

Timothy Fitz — Tue, 17 Feb 2009 04:49:49 +0000

This is almost exactly what we do at IMVU. There are some additional wrinkles when you need to change high volume tables or large data size tables, but otherwise the process is almost exactly the same.

By: Chris

Chris — Mon, 16 Feb 2009 23:58:51 +0000

For something where you’re already deployed this sounds great. Anymore I if I find I’ve got to have a schema, then I do something similar to a Generic Entity Cloud that my step dad was involved in documenting. A really simple (and rather broken) implementation is here: http://github.com/cdent/bzhl7/blob/3e9eff8a0c9a1bd1c668b53a4e2bb786ff3586e4/GEC.pm