<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Versioning on Ash Tewari</title><link>https://www.tewari.info/tag/versioning/</link><description>Recent content in Versioning on Ash Tewari</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 19 Feb 2008 03:05:52 +0000</lastBuildDate><atom:link href="https://www.tewari.info/tag/versioning/feed.xml" rel="self" type="application/rss+xml"/><item><title>Database Schema Version Control Tool</title><link>https://www.tewari.info/2008/02/18/dbupdater-database-schema-version-control/</link><pubDate>Tue, 19 Feb 2008 03:05:52 +0000</pubDate><guid isPermaLink="false">http://www.tewari.info/2008/02/18/dbupdater-database-schema-version-control/</guid><description>&lt;p&gt;It is essential to treat database schema as source code and apply all the norms and best practices applicable to it. From what I hear and read, database schema version control is non-existent in too many projects.&lt;/p&gt;
&lt;p&gt;Various techniques to accomplish version control of database schemas have been discussed and published. Martin Fowler and Pramod Sadagale has written a comprehensive article on &lt;a href="http://martinfowler.com/articles/evodb.html"&gt;Evolutionary Database Design&lt;/a&gt;. It is a must-read for everyone involved with database development.&lt;/p&gt;</description></item></channel></rss>