<?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>Microsoft SQL Server Release Services : SQL Server 2005</title><link>http://blogs.msdn.com/sqlreleaseservices/archive/tags/SQL+Server+2005/default.aspx</link><description>Tags: SQL Server 2005</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>A changed approach to Service Packs</title><link>http://blogs.msdn.com/sqlreleaseservices/archive/2008/04/27/a-changed-approach-to-service-packs.aspx</link><pubDate>Sun, 27 Apr 2008 18:26:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8431954</guid><dc:creator>matthiab</dc:creator><slash:comments>9</slash:comments><comments>http://blogs.msdn.com/sqlreleaseservices/comments/8431954.aspx</comments><wfw:commentRss>http://blogs.msdn.com/sqlreleaseservices/commentrss.aspx?PostID=8431954</wfw:commentRss><description>In reference to the recent announcement of a Service Pack 3 for SQL Server 2005 I wanted to take some time and elaborate a bit over a modified development approach we’ll be taking for SQL Server Servicing releases. With our recent SP3 announcement we...(&lt;a href="http://blogs.msdn.com/sqlreleaseservices/archive/2008/04/27/a-changed-approach-to-service-packs.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=8431954" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/sqlreleaseservices/archive/tags/SQL+Server+2005/default.aspx">SQL Server 2005</category><category domain="http://blogs.msdn.com/sqlreleaseservices/archive/tags/SQL+Server+Service+Pack+Strategy/default.aspx">SQL Server Service Pack Strategy</category></item><item><title>SQL Server Express 2005 is now supported by XPe and WEPOS platforms</title><link>http://blogs.msdn.com/sqlreleaseservices/archive/2007/06/22/sql-server-express-2005-is-now-supported-by-xpe-and-wepos-platforms.aspx</link><pubDate>Fri, 22 Jun 2007 19:15:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:3464792</guid><dc:creator>SavithaP</dc:creator><slash:comments>1</slash:comments><comments>http://blogs.msdn.com/sqlreleaseservices/comments/3464792.aspx</comments><wfw:commentRss>http://blogs.msdn.com/sqlreleaseservices/commentrss.aspx?PostID=3464792</wfw:commentRss><description>We have received numerous customer requests for supporting SQL Server 2005 on XPe and WEPOS. Listening to your requests, we are now happy to announce the support for SQL Server 2005 Express Edition starting with Service Pack 2 on Windows XP Embedded Service...(&lt;a href="http://blogs.msdn.com/sqlreleaseservices/archive/2007/06/22/sql-server-express-2005-is-now-supported-by-xpe-and-wepos-platforms.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=3464792" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/sqlreleaseservices/archive/tags/SQL+Server+2005/default.aspx">SQL Server 2005</category><category domain="http://blogs.msdn.com/sqlreleaseservices/archive/tags/SQL+Server+2005+SP2+Express+Edition/default.aspx">SQL Server 2005 SP2 Express Edition</category></item><item><title>Cumulative update package 2 for SQL Server 2005 Service Pack 2 is available</title><link>http://blogs.msdn.com/sqlreleaseservices/archive/2007/06/22/cumulative-update-package-2-for-sql-server-2005-service-pack-2-is-available.aspx</link><pubDate>Fri, 22 Jun 2007 07:25:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:3452904</guid><dc:creator>matthiab</dc:creator><slash:comments>1</slash:comments><comments>http://blogs.msdn.com/sqlreleaseservices/comments/3452904.aspx</comments><wfw:commentRss>http://blogs.msdn.com/sqlreleaseservices/commentrss.aspx?PostID=3452904</wfw:commentRss><description>&lt;P&gt;Per previously announced revised Servicing Model we released the second scheduled cumulative update for SQL Server 2005 to the support organization earlier this week. Build number is 3175.&lt;/P&gt;
&lt;P&gt;Information on this cumulative update (CU):&amp;nbsp;&lt;A href="http://support.microsoft.com/kb/936305"&gt;http://support.microsoft.com/kb/936305&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Information on how to obtain this CU: &lt;A href="http://support.microsoft.com/kb/935195"&gt;http://support.microsoft.com/kb/935195&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;Thanks, Matthias Berndt&lt;/P&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=3452904" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/sqlreleaseservices/archive/tags/SQL+Server+2005/default.aspx">SQL Server 2005</category></item><item><title>SQL Server Hotfix Release Revised</title><link>http://blogs.msdn.com/sqlreleaseservices/archive/2007/04/06/sql-server-hotfix-release-revised.aspx</link><pubDate>Sat, 07 Apr 2007 01:17:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2042401</guid><dc:creator>Keith Fang</dc:creator><slash:comments>6</slash:comments><comments>http://blogs.msdn.com/sqlreleaseservices/comments/2042401.aspx</comments><wfw:commentRss>http://blogs.msdn.com/sqlreleaseservices/commentrss.aspx?PostID=2042401</wfw:commentRss><description>&lt;P class=MsoNormal style="MARGIN: 0in 0in 0pt; LINE-HEIGHT: normal"&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'; mso-fareast-font-family: 'Times New Roman'"&gt;In response to customer feedback, SQL Server team has revised the mechanism to deliver &lt;/SPAN&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-size: 11.0pt"&gt;hotfixes&lt;/SPAN&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'; mso-fareast-font-family: 'Times New Roman'"&gt; on reported bugs with a new model called Incremental Servicing Model (ISM). The objective is to deliver high quality fixes within an acceptable amount of time and on a predictable schedule. &lt;/SPAN&gt;&lt;SPAN style="FONT-SIZE: 12pt; FONT-FAMILY: 'Arial','sans-serif'; mso-fareast-font-family: 'Times New Roman'"&gt;&lt;?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 0pt; LINE-HEIGHT: normal"&gt;&lt;SPAN style="FONT-SIZE: 12pt; FONT-FAMILY: 'Arial','sans-serif'; mso-fareast-font-family: 'Times New Roman'"&gt;&amp;nbsp;&lt;o:p&gt;&lt;/o:p&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 0pt; LINE-HEIGHT: normal"&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'; mso-fareast-font-family: 'Times New Roman'"&gt;We have&amp;nbsp;moved away from current “priority driven” &lt;/SPAN&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-size: 11.0pt"&gt;hotfix&lt;/SPAN&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'; mso-fareast-font-family: 'Times New Roman'"&gt; release model to a scheduled delivery model in which a customer can get a &lt;/SPAN&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-size: 11.0pt"&gt;hotfix&lt;/SPAN&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'; mso-fareast-font-family: 'Times New Roman'"&gt; to service their most critical situations with a short turn-around time or a fix that has undergone higher levels of testing is released on a scheduled basis. &amp;nbsp;As a result&amp;nbsp;we created the two delivery mechanisms outlined below:&lt;/SPAN&gt;&lt;SPAN style="FONT-SIZE: 12pt; FONT-FAMILY: 'Arial','sans-serif'; mso-fareast-font-family: 'Times New Roman'"&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 0pt; LINE-HEIGHT: normal"&gt;&lt;SPAN style="FONT-SIZE: 12pt; FONT-FAMILY: 'Arial','sans-serif'; mso-fareast-font-family: 'Times New Roman'"&gt;&amp;nbsp;&lt;o:p&gt;&lt;/o:p&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 0pt; LINE-HEIGHT: normal"&gt;&lt;B style="mso-bidi-font-weight: normal"&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'; mso-fareast-font-family: Verdana"&gt;1)&lt;/SPAN&gt;&lt;/B&gt;&lt;B style="mso-bidi-font-weight: normal"&gt;&lt;SPAN style="FONT-SIZE: 7pt; FONT-FAMILY: 'Arial','sans-serif'; mso-fareast-font-family: Verdana"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;/B&gt;&lt;B style="mso-bidi-font-weight: normal"&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'; mso-fareast-font-family: 'Times New Roman'"&gt;An On-Demand &lt;/SPAN&gt;&lt;/B&gt;&lt;B style="mso-bidi-font-weight: normal"&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-size: 11.0pt"&gt;Hotfix&lt;/SPAN&gt;&lt;/B&gt;&lt;B style="mso-bidi-font-weight: normal"&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'; mso-fareast-font-family: 'Times New Roman'"&gt; request:&lt;o:p&gt;&lt;/o:p&gt;&lt;/SPAN&gt;&lt;/B&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 0pt 0.5in; TEXT-INDENT: -0.25in; LINE-HEIGHT: normal"&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'; mso-fareast-font-family: Verdana"&gt;a.&lt;/SPAN&gt;&lt;SPAN style="FONT-SIZE: 7pt; FONT-FAMILY: 'Arial','sans-serif'; mso-fareast-font-family: Verdana"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'; mso-fareast-font-family: 'Times New Roman'"&gt;The issue must meet the criteria for this request (including a lack of a viable work-around, critical business impact, etc.)&lt;o:p&gt;&lt;/o:p&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 0pt 0.5in; TEXT-INDENT: -0.25in; LINE-HEIGHT: normal"&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'; mso-fareast-font-family: Verdana"&gt;b.&lt;/SPAN&gt;&lt;SPAN style="FONT-SIZE: 7pt; FONT-FAMILY: 'Arial','sans-serif'; mso-fareast-font-family: Verdana"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'; mso-fareast-font-family: 'Times New Roman'"&gt;May be requested by any customer regardless of their support offering as long as it met the above bar.&amp;nbsp; &lt;o:p&gt;&lt;/o:p&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 0pt 0.5in; TEXT-INDENT: -0.25in; LINE-HEIGHT: normal"&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'; mso-fareast-font-family: Verdana"&gt;c.&lt;/SPAN&gt;&lt;SPAN style="FONT-SIZE: 7pt; FONT-FAMILY: 'Arial','sans-serif'; mso-fareast-font-family: Verdana"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'; mso-fareast-font-family: 'Times New Roman'"&gt;Is released on or before a mutually agreed date based on customer’s need&lt;o:p&gt;&lt;/o:p&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 0pt 0.5in; TEXT-INDENT: -0.25in; LINE-HEIGHT: normal"&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'; mso-fareast-font-family: Verdana"&gt;d.&lt;/SPAN&gt;&lt;SPAN style="FONT-SIZE: 7pt; FONT-FAMILY: 'Arial','sans-serif'; mso-fareast-font-family: Verdana"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'; mso-fareast-font-family: 'Times New Roman'"&gt;This &lt;/SPAN&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-size: 11.0pt"&gt;hotfix&lt;/SPAN&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'; mso-fareast-font-family: 'Times New Roman'"&gt; build could contain one or more fixes.&lt;o:p&gt;&lt;/o:p&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 0pt 1in; LINE-HEIGHT: normal"&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'; mso-fareast-font-family: 'Times New Roman'"&gt;&lt;o:p&gt;&amp;nbsp;&lt;/o:p&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 0pt; LINE-HEIGHT: normal"&gt;&lt;B style="mso-bidi-font-weight: normal"&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'; mso-fareast-font-family: Verdana"&gt;2)&lt;/SPAN&gt;&lt;/B&gt;&lt;B style="mso-bidi-font-weight: normal"&gt;&lt;SPAN style="FONT-SIZE: 7pt; FONT-FAMILY: 'Arial','sans-serif'; mso-fareast-font-family: Verdana"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;/B&gt;&lt;B style="mso-bidi-font-weight: normal"&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'; mso-fareast-font-family: 'Times New Roman'"&gt;Cumulative Update: &lt;o:p&gt;&lt;/o:p&gt;&lt;/SPAN&gt;&lt;/B&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 0pt 0.5in; TEXT-INDENT: -0.25in; LINE-HEIGHT: normal"&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'; mso-fareast-font-family: Verdana"&gt;a.&lt;/SPAN&gt;&lt;SPAN style="FONT-SIZE: 7pt; FONT-FAMILY: 'Arial','sans-serif'; mso-fareast-font-family: Verdana"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'; mso-fareast-font-family: 'Times New Roman'"&gt;May be requested by any customer regardless of their support offering.&lt;o:p&gt;&lt;/o:p&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 0pt 0.5in; TEXT-INDENT: -0.25in; LINE-HEIGHT: normal"&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'; mso-fareast-font-family: Verdana"&gt;b.&lt;/SPAN&gt;&lt;SPAN style="FONT-SIZE: 7pt; FONT-FAMILY: 'Arial','sans-serif'; mso-fareast-font-family: Verdana"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'; mso-fareast-font-family: 'Times New Roman'"&gt;Is released every 2 months.&lt;o:p&gt;&lt;/o:p&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 0pt 0.5in; TEXT-INDENT: -0.25in; LINE-HEIGHT: normal"&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'; mso-fareast-font-family: Verdana"&gt;c.&lt;/SPAN&gt;&lt;SPAN style="FONT-SIZE: 7pt; FONT-FAMILY: 'Arial','sans-serif'; mso-fareast-font-family: Verdana"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'; mso-fareast-font-family: 'Times New Roman'"&gt;Is a Cumulative Update build containing:&lt;o:p&gt;&lt;/o:p&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class=MsoListParagraphCxSpFirst style="MARGIN: 0in 0in 0pt 0.75in; TEXT-INDENT: -0.25in; LINE-HEIGHT: normal; mso-add-space: auto; mso-list: l0 level1 lfo1"&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'; mso-fareast-font-family: Arial"&gt;&lt;SPAN style="mso-list: Ignore"&gt;1.&lt;SPAN style="FONT: 7pt 'Times New Roman'"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'; mso-fareast-font-family: 'Times New Roman'"&gt;All previous on-demand &lt;/SPAN&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-size: 11.0pt"&gt;hotfixes&lt;/SPAN&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'; mso-fareast-font-family: 'Times New Roman'"&gt; to-date&lt;o:p&gt;&lt;/o:p&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class=MsoListParagraphCxSpLast style="MARGIN: 0in 0in 0pt 0.75in; TEXT-INDENT: -0.25in; LINE-HEIGHT: normal; mso-add-space: auto; mso-list: l0 level1 lfo1"&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'; mso-fareast-font-family: Arial"&gt;&lt;SPAN style="mso-list: Ignore"&gt;2.&lt;SPAN style="FONT: 7pt 'Times New Roman'"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'; mso-fareast-font-family: 'Times New Roman'"&gt;Fixes for issues that meet hotfix acceptance criteria which considers the work-around availability, customer impact, reproducibility, complexity of code needing to be changed, etc.&lt;o:p&gt;&lt;/o:p&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 0pt 9pt; TEXT-INDENT: -9pt; LINE-HEIGHT: normal"&gt;&lt;SPAN style="FONT-SIZE: 7pt; FONT-FAMILY: 'Arial','sans-serif'; mso-fareast-font-family: Verdana"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'; mso-fareast-font-family: 'Times New Roman'"&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="FONT-SIZE: 10pt; LINE-HEIGHT: 115%; FONT-FAMILY: 'Arial','sans-serif'; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"&gt;While we are rolling out this revised model,&amp;nbsp;there are several other projects are&amp;nbsp;being done concurrently to focus on&amp;nbsp;improving the quality of SQL Server at&amp;nbsp;ship time to&amp;nbsp;reduce the need for hotfixes of this nature&lt;/SPAN&gt;&lt;/P&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=2042401" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/sqlreleaseservices/archive/tags/SQL+Server+2005/default.aspx">SQL Server 2005</category></item><item><title>SQL 2005 SP2 - delivered!</title><link>http://blogs.msdn.com/sqlreleaseservices/archive/2007/02/19/sql-2005-sp2-delivered.aspx</link><pubDate>Tue, 20 Feb 2007 03:10:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1719739</guid><dc:creator>GrantC</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/sqlreleaseservices/comments/1719739.aspx</comments><wfw:commentRss>http://blogs.msdn.com/sqlreleaseservices/commentrss.aspx?PostID=1719739</wfw:commentRss><description>&lt;P&gt;Months of effort by hundreds of people (including many of you, I'm sure) culminated this morning in the release of &lt;A class="" href="http://www.microsoft.com/sql/sp2.mspx" target=_blank mce_href="http://www.microsoft.com/sql/sp2.mspx"&gt;SQL 2005 SP2&lt;/A&gt;.&amp;nbsp; This was a servicing release defined and driven largely by your feedback and bug reports.&amp;nbsp; There are also some big ticket items such as proper Windows Vista support and integration with Office 2007 - be sure to check out the &lt;A class="" href="http://go.microsoft.com/fwlink/?LinkId=71711" target=_blank mce_href="http://go.microsoft.com/fwlink/?LinkId=71711"&gt;What's New doc&lt;/A&gt;&amp;nbsp;and the &lt;A class="" href="http://www.microsoft.com/presspass/press/2007/feb07/02-19SQLSP2PR.mspx" target=_blank mce_href="http://www.microsoft.com/presspass/press/2007/feb07/02-19SQLSP2PR.mspx"&gt;press release&lt;/A&gt; for the full scoop.&amp;nbsp; Keep that feedback &lt;A class="" href="http://go.microsoft.com/fwlink/?LinkId=34178" target=_blank mce_href="http://go.microsoft.com/fwlink/?LinkId=34178"&gt;flowing in&lt;/A&gt; so we can incorporate it into future releases such as Katmai, the next major release of SQL Server.&amp;nbsp; Also we hope you'll join us for a &lt;A class="" href="http://go.microsoft.com/fwlink/?LinkId=83350" target=_blank mce_href="http://go.microsoft.com/fwlink/?LinkId=83350"&gt;TechNet webchat&lt;/A&gt; on March 6th at 9am PST with members of the SQL Server development team.&amp;nbsp; In the meantime if you have questions about SP2 your best bet is visiting the &lt;A class="" href="http://go.microsoft.com/fwlink/?LinkId=56089" target=_blank mce_href="http://go.microsoft.com/fwlink/?LinkId=56089"&gt;MSDN forums&lt;/A&gt;.&amp;nbsp; It feels really great to get this release out, and we hope you agree!&lt;/P&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=1719739" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/sqlreleaseservices/archive/tags/SQL+Server+2005/default.aspx">SQL Server 2005</category></item></channel></rss>