<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.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>SQL Server Compatibility Mode</title><link>http://blogs.technet.com/andrew/archive/2008/03/25/sql-server-compatibility-mode.aspx</link><description>I drew the short straw at the 2008 Launch event last week in Birmingham; speak for one hour on upgrading SQL Server.&amp;#160; I found this very difficult because on the one hand you can usually just do the upgrade, once you have done all the pre-requisite</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: SQL Server Compatibility Mode</title><link>http://blogs.technet.com/andrew/archive/2008/03/25/sql-server-compatibility-mode.aspx#3143964</link><pubDate>Wed, 29 Oct 2008 13:09:57 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3143964</guid><dc:creator>Michael Falconer</dc:creator><description>&lt;p&gt;You mention in your article 'The reason I do like compatibility mode is that while it is on you can then set up profiler to watch for any events that use this feature.'. Can you provide any more information on this? We've a number of SQL 2000 databases we want to migrate but we will be running them in compatability mode to start with.&lt;/p&gt;
&lt;p&gt;I see there is a deprecation section in the events available to be tracked in profiler.&lt;/p&gt;</description></item></channel></rss>