<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://decav.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Setting Up SQL 2005 Deployments - Migrating from SQL 2000</title><link>http://decav.com/blogs/andre/archive/2006/04/11/10.aspx</link><description>Setting up Microsoft SQL Server 2005 and migrating existing data from SQL 2000 is a relatively easy task if your implementation is enclosed and you do not touch default settings. There are, however many subtleties that can cause SQL migrations to go horribly</description><dc:language>en</dc:language><generator>CommunityServer 2007 (Build: 20423.869)</generator><item><title>re: Setting Up SQL 2005 Deployments - Migrating from SQL 2000</title><link>http://decav.com/blogs/andre/archive/2006/04/11/10.aspx#27</link><pubDate>Fri, 19 May 2006 14:11:23 GMT</pubDate><guid isPermaLink="false">1a6c50a2-1cc5-440d-a734-51a167eba982:27</guid><dc:creator>Anonymous</dc:creator><description>Great, it solved my problems with collations tnks&lt;img src="http://decav.com/aggbug.aspx?PostID=27" width="1" height="1"&gt;</description></item></channel></rss>