<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"><channel><title>Versioning the Database</title><link>http://blogs.msdn.com/b/buckwoody/archive/2009/01/27/versioning-the-database.aspx</link><description>If you write apps that hit a database that you own, then you probably want version control on the database itself. I always script out the initial database, and version that script. I also script the changes, and version those, and then script the entire</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Versioning the Database</title><link>http://blogs.msdn.com/b/buckwoody/archive/2009/01/27/versioning-the-database.aspx#10072480</link><pubDate>Wed, 06 Oct 2010 22:51:02 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10072480</guid><dc:creator>Brian Krebs</dc:creator><description>&lt;p&gt;I like that you are attempting to solve an age-old IT conundrum in a pragmatic way. &amp;nbsp;I see a couple of downsides to your approach though, and you mentioned a few in your final paragraph. &amp;nbsp;There is really no true control since the user can change objects without checking in.&lt;/p&gt;
&lt;p&gt;A new, innovative software product called DBVS solves all of these problems in an elegant way. &amp;nbsp;When a database object is checked in, the DBVS server connects to that database and extracts the object&amp;#39;s metadata in an XML format and versions it in a SCM tool of your choice. &amp;nbsp;That means there is no need to version SQL scripts at all.&lt;/p&gt;
&lt;p&gt;Find out more about DBVS at &lt;a rel="nofollow" target="_new" href="http://www.dbvsys.com"&gt;http://www.dbvsys.com&lt;/a&gt;. &amp;nbsp;Comments and suggestions are always welcome. &amp;nbsp;I&amp;#39;d be interested to hear your thoughts.&lt;/p&gt;
&lt;p&gt;Brian Krebs&lt;/p&gt;
&lt;p&gt;Chief Technical Officer&lt;/p&gt;
&lt;p&gt;Database Versioning Systems&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10072480" width="1" height="1"&gt;</description></item><item><title>re: Versioning the Database</title><link>http://blogs.msdn.com/b/buckwoody/archive/2009/01/27/versioning-the-database.aspx#9382380</link><pubDate>Thu, 29 Jan 2009 07:43:52 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9382380</guid><dc:creator>Bill Ramos</dc:creator><description>&lt;p&gt;Funny you should bring this topic up on the same day that I recieved my plaque for versioning database objects using source control systems from back in 1999. Check out &lt;a rel="nofollow" target="_new" href="http://tinyurl.com/dlynbv"&gt;http://tinyurl.com/dlynbv&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Bill Ramos&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9382380" width="1" height="1"&gt;</description></item></channel></rss>