http://sqlblog.com/blogs/denis_gobo/archive/tags/Version+Control/default.aspxTags: Version ControlenCommunityServer 2.1 SP2 (Build: 61129.1)http://sqlblog.com/blogs/denis_gobo/archive/2008/02/04/4864.aspxMon, 04 Feb 2008 15:34:00 GMT21093a07-8b3d-42db-8cbf-3350fcbf5496:4864Denis Gobo9http://sqlblog.com/blogs/denis_gobo/comments/4864.aspxhttp://sqlblog.com/blogs/denis_gobo/commentrss.aspx?PostID=4864http://sqlblog.com/blogs/denis_gobo/rsscomments.aspx?PostID=4864<P>CodingHorror has a blogpost titled <A class=title-link href="http://www.codinghorror.com/blog/archives/001050.html">Get Your Database Under Version Control</A></P> <P>It is suggested that you also keep the data in version control. I am reading through the comments and I am amazed. One person writes "Once you have used ActiveRecord Migrations it is very hard to go back!"</P> <P>This might work for a small or medium size database. My database is well over a terabyte, how would you keep that data under version control? Data gets modified every day. Some of the data is encrypted. Some of the data gets inserted into audit tables. Data gets replicated to other servers/databases. There are jobs that pull in data from real time systems every second. I do have different versions of DBs on staging and QA servers but only one on the production server. Changes have to go through change management, you have to open a ticket to do a change. This is not something you would do on a daily basis.</P> <P>What is your opinion? Do you have the schema in version control? What about the data itself?</P><img src="http://sqlblog.com/aggbug.aspx?PostID=4864" width="1" height="1">Version Control