<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Emad Ibrahim - Latest Comments in Database Schema Compare &amp;amp; Upgrade</title><link>http://emadibrahim.disqus.com/</link><description></description><language>en</language><lastBuildDate>Tue, 29 Jul 2008 04:02:22 -0000</lastBuildDate><item><title>Re: Database Schema Compare &amp;amp; Upgrade</title><link>http://www.emadibrahim.com/2008/07/10/database-schema-compare-upgrade/#comment-1601800</link><description>The Database comparison tools in DB Pro really aren't migrations.  If you're looking for that, check out my post comparing some .NET Migrations here:&lt;br&gt;&lt;a href="http://flux88.com/NETDatabaseMigrationToolRoundup.aspx" rel="nofollow"&gt;.NET Database Migration Tool Roundup&lt;/a&gt;&lt;br&gt;&lt;br&gt;The Schema Comparison tool cannot help you when you are deploying a volatile change, such as adding a new NOT NULL column to a table that has existing data.  You have to customize the script.  It doesn't handle refactorings where you change the datatype of a column.  Again you have to futz with the script.&lt;br&gt;&lt;br&gt;Migrations capture the evolution of the database and applies these changes safely and in order.&lt;br&gt;&lt;br&gt;Also I'd like to plug RedGate's SQL Compare, which is far better than DB Pro's Schema Comparison.  It does cost money, but then again so does DB Pro.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ben Scheirman</dc:creator><pubDate>Tue, 29 Jul 2008 04:02:22 -0000</pubDate></item></channel></rss>