<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>leinadium &#187; utf8</title>
	<atom:link href="http://www.leinadium.com/tag/utf8/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.leinadium.com</link>
	<description>Techhead. Codewarrior. Legalnerd.</description>
	<lastBuildDate>Fri, 02 Sep 2011 20:09:28 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>MySql Migration Toolkit MSSQL latin1 to MySql utf8</title>
		<link>http://www.leinadium.com/code/mysql-migration-toolkit-mssql-latin1-to-mysql-utf8/</link>
		<comments>http://www.leinadium.com/code/mysql-migration-toolkit-mssql-latin1-to-mysql-utf8/#comments</comments>
		<pubDate>Fri, 23 Jan 2009 10:49:12 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[code]]></category>
		<category><![CDATA[charset]]></category>
		<category><![CDATA[mysql]]></category>
		<category><![CDATA[utf8]]></category>

		<guid isPermaLink="false">http://217.11.59.22/leinadium/?p=15</guid>
		<description><![CDATA[We&#8217;ve all been there. The dreaded Umlaute and special characters have been turned into minced words by some character encoding incompatibility. When converting a database from MSSQL(2000) to MYSQL (v5) I must have spent days trying to figure this problem out. Some people have come up with very creative albeit complicated solutions: http://www.oreillynet.com/onlamp/blog/2006/01/turning_mysql_data_in_latin1_t.html Instead, I [...]]]></description>
			<content:encoded><![CDATA[<p>We&#8217;ve all been there.<br />
The dreaded Umlaute and special characters have been turned into minced words by some character encoding incompatibility.</p>
<p>When converting a database from MSSQL(2000) to MYSQL (v5) I must have spent days trying to figure this problem out. Some people have come up with very creative albeit complicated solutions:<br />
<a href="http://www.oreillynet.com/onlamp/blog/2006/01/turning_mysql_data_in_latin1_t.html">http://www.oreillynet.com/onlamp/blog/2006/01/turning_mysql_data_in_latin1_t.html</a></p>
<p>Instead, I found this:<br />
<a href="http://forums.mysql.com/read.php?104,124017,124790#msg-124790">http://forums.mysql.com/read.php?104,124017,124790#msg-124790</a><br />
Thank you Miguel.<br />
The solution is simple:</p>
<p>In Migration Toolkit&#8217;s first step, where you select the source and target db, in Advanced &gt;&gt; option, use the following jdbc connection string for MSSQL:<br />
jdbc:jtds:sqlserver://server:1433/database;user=user;password=password;useUnicode=true;domain=</p>
<p>And this one for MySQL:<br />
jdbc:mysql://server:3306/?user=user&amp;password=password&amp;useServerPrepStmts=false&amp;useUnicode=true</p>
<p>Forget the utf-8 character encoding that you see elsewhere. useUnicode rules. And so does Miguel.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.leinadium.com/code/mysql-migration-toolkit-mssql-latin1-to-mysql-utf8/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
	</channel>
</rss>

