<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.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>An important change for the Microsoft Lifecycle Support Policy….</title><link>http://blogs.msdn.com/b/psssql/archive/2010/04/13/an-important-change-for-the-microsoft-lifecycle-support-policy.aspx</link><description>Over the past few months I’ve filed some posts on our blog regarding our support lifecycle policies because I know sometimes this topic can get very confusing: http://blogs.msdn.com/psssql/archive/2010/02/17/mainstream-vs-extended-support-and-sql-server</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: An important change for the Microsoft Lifecycle Support Policy….</title><link>http://blogs.msdn.com/b/psssql/archive/2010/04/13/an-important-change-for-the-microsoft-lifecycle-support-policy.aspx#9996698</link><pubDate>Thu, 15 Apr 2010 18:28:47 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9996698</guid><dc:creator>Mary Myers</dc:creator><description>&lt;p&gt;I think that you should have released a 'last service pack' after all the cummulative updates PRIOR to establishing a life cycle date especially when some Microsoft applications require CU# after the last service pack (like SharePoint, CRM, GP, SL, etc.). &amp;nbsp;I think it would have helped your support team as well as any SQL DBA team to rollout the last service pack that would include all CU's. Now you have to keep all those CU's in your download area too...doesn't seem efficient or effective for anyone does it. &lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9996698" width="1" height="1"&gt;</description></item></channel></rss>