<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://sqlblog.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>Search results matching tags 'Releases' and 'Trends'</title><link>http://sqlblog.com/search/SearchResults.aspx?o=DateDescending&amp;tag=Releases,Trends&amp;orTags=0</link><description>Search results matching tags 'Releases' and 'Trends'</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP2 (Build: 61129.1)</generator><item><title>Slipstreaming Hot Fixes and Service Packs</title><link>http://sqlblog.com/blogs/kevin_kline/archive/2006/12/29/slipstreaming-hot-fixes-and-service-packs.aspx</link><pubDate>Fri, 29 Dec 2006 18:42:00 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:505</guid><dc:creator>KKline</dc:creator><description>&lt;P&gt;I've been getting requests from users concerning the best way to roll out new service packs and hot fixes to their SQL Server computers.&amp;nbsp; A perenial question that always seems to come up is "Why doesn't Microsoft slipstream (that is, add the hot fixes and service packs directly into the product) updates for SQL Server?"&lt;BR&gt;&lt;BR&gt;This is an important philosophic question about what is the best way to support a production software product.&amp;nbsp; It all comes down to mindset and how you prioritize various issues.&amp;nbsp; I can't pretend to speak for Microsoft, but you can get some great insight into these issues by reading Euan Garden's, a person I emminently respect,&amp;nbsp;blog posts on this topic at &lt;A href="http://blogs.msdn.com/euanga/archive/2006/04/27/584637.aspx"&gt;http://blogs.msdn.com/euanga/archive/2006/04/27/584637.aspx&lt;/A&gt;.&lt;BR&gt;&lt;BR&gt;Let me, and more importantly Euan, know what you think.&lt;BR&gt;&lt;BR&gt;Cheers,&lt;BR&gt;&lt;BR&gt;-Kevin&lt;/P&gt;</description></item></channel></rss>