<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Database Schema Compare &amp; Upgrade</title>
	<atom:link href="http://www.emadibrahim.com/2008/07/10/database-schema-compare-upgrade/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.emadibrahim.com/2008/07/10/database-schema-compare-upgrade/</link>
	<description>web development, tech reviews, tips, tricks, blogging</description>
	<lastBuildDate>Sun, 07 Mar 2010 18:27:34 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ben Scheirman</title>
		<link>http://www.emadibrahim.com/2008/07/10/database-schema-compare-upgrade/comment-page-1/#comment-320</link>
		<dc:creator>Ben Scheirman</dc:creator>
		<pubDate>Tue, 29 Jul 2008 04:02:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.emadibrahim.com/2008/07/10/database-schema-compare-upgrade/#comment-320</guid>
		<description>The Database comparison tools in DB Pro really aren&#039;t migrations.  If you&#039;re looking for that, check out my post comparing some .NET Migrations here:
&lt;a href=&quot;http://flux88.com/NETDatabaseMigrationToolRoundup.aspx&quot; rel=&quot;nofollow&quot;&gt;.NET Database Migration Tool Roundup&lt;/a&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&#039;t handle refactorings where you change the datatype of a column.  Again you have to futz with the script.

Migrations capture the evolution of the database and applies these changes safely and in order.

Also I&#039;d like to plug RedGate&#039;s SQL Compare, which is far better than DB Pro&#039;s Schema Comparison.  It does cost money, but then again so does DB Pro.</description>
		<content:encoded><![CDATA[<p>The Database comparison tools in DB Pro really aren&#8217;t migrations.  If you&#8217;re looking for that, check out my post comparing some .NET Migrations here:<br />
<a href="http://flux88.com/NETDatabaseMigrationToolRoundup.aspx" rel="nofollow">.NET Database Migration Tool Roundup</a></p>
<p>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&#8217;t handle refactorings where you change the datatype of a column.  Again you have to futz with the script.</p>
<p>Migrations capture the evolution of the database and applies these changes safely and in order.</p>
<p>Also I&#8217;d like to plug RedGate&#8217;s SQL Compare, which is far better than DB Pro&#8217;s Schema Comparison.  It does cost money, but then again so does DB Pro.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Scheirman</title>
		<link>http://www.emadibrahim.com/2008/07/10/database-schema-compare-upgrade/comment-page-1/#comment-390</link>
		<dc:creator>Ben Scheirman</dc:creator>
		<pubDate>Tue, 29 Jul 2008 02:02:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.emadibrahim.com/2008/07/10/database-schema-compare-upgrade/#comment-390</guid>
		<description>The Database comparison tools in DB Pro really aren&#039;t migrations.  If you&#039;re looking for that, check out my post comparing some .NET Migrations here:&lt;br&gt;&lt;a href=&quot;http://flux88.com/NETDatabaseMigrationToolRoundup.aspx&quot; rel=&quot;nofollow&quot;&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&#039;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&#039;d like to plug RedGate&#039;s SQL Compare, which is far better than DB Pro&#039;s Schema Comparison.  It does cost money, but then again so does DB Pro.</description>
		<content:encoded><![CDATA[<p>The Database comparison tools in DB Pro really aren&#8217;t migrations.  If you&#8217;re looking for that, check out my post comparing some .NET Migrations here:<br /><a href="http://flux88.com/NETDatabaseMigrationToolRoundup.aspx" rel="nofollow">.NET Database Migration Tool Roundup</a></p>
<p>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&#8217;t handle refactorings where you change the datatype of a column.  Again you have to futz with the script.</p>
<p>Migrations capture the evolution of the database and applies these changes safely and in order.</p>
<p>Also I&#8217;d like to plug RedGate&#8217;s SQL Compare, which is far better than DB Pro&#8217;s Schema Comparison.  It does cost money, but then again so does DB Pro.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
