<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://www.townx.org" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>townx - MySQL migration suite - Comments</title>
 <link>http://www.townx.org/blog/elliot/mysql_migration_suite</link>
 <description>Comments for &quot;MySQL migration suite&quot;</description>
 <language>en</language>
<item>
 <title>MySQL migration suite</title>
 <link>http://www.townx.org/blog/elliot/mysql_migration_suite</link>
 <description>&lt;p&gt;This &lt;a href=&quot;http://www.mysql.com/products/migration-suite/&quot;&gt;nifty piece of software&lt;/a&gt; could be useful. Currently supports Access and Oracle. Perhaps this is an indication of where MySQL thinks the competition is: at the two extremes of the market, the big corporate back end and the desktop. I&#039;ve just watched the &lt;a href=&quot;http://www.mysql.com/products/migration-suite/tutorials/AccessMigrationTutorial.html&quot;&gt;demo of an Access migration&lt;/a&gt;, and it looks really smooth. I used to use &lt;a href=&quot;http://www.mysqlfront.de/&quot;&gt;MySQL-Front&lt;/a&gt; to migrate Access to MySQL, when MySQL-Front was freeware and before it turned commercial. Between these two states, development halted altogether, and the product went out of step with MySQL versions. I learned an important lesson about proprietary software when this happened, leaving me stuck with a version which wouldn&#039;t work with my version of MySQL: I vowed never to use proprietary software again for anything important.&lt;/p&gt;
</description>
 <comments>http://www.townx.org/blog/elliot/mysql_migration_suite#comments</comments>
 <pubDate>Wed, 20 Apr 2005 13:47:00 -0500</pubDate>
 <dc:creator>elliot</dc:creator>
 <guid isPermaLink="false">112 at http://www.townx.org</guid>
</item>
</channel>
</rss>
