Microsoft Delivers SQL Server 2005 SP3 -- Visual Studio Magazine

Microsoft Delivers SQL Server 2005 SP3

Microsoft ratcheted up its product support for SQL Server 2005 by releasing Service Pack 3 (SP3) on Monday, along with SP3 Cumulative Update 1.

By Herb Torrens
12/16/2008

Microsoft ratcheted up its product support for SQL Server 2005 by releasing Service Pack 3 (SP3) on Monday, along with SP3 Cumulative Update 1. On the same day, the company also released Cumulative Update 11 for SQL Server 2005 Service Pack 2 (SP2).

If that weren't enough, the company offered incentives for Microsoft's partners and Microsoft Dynamics customers to jump to SQL Server 2008, which was released as a product last summer.

Microsoft is updating its price list on January 1, 2009 and will replace the runtime for SQL Server 2005 with that of Microsoft SQL Server 2008, according to a Microsoft Dynamics blog.

"Customers who have licensed Microsoft SQL 2008-Runtime and are current on the Business Ready Enhancement Plan as of January 1, 2009 will be entitled to an upgrade to Microsoft SQL Server 2008," the blog explained.

Features in SQL Server SP3 include "supportability enhancements," plus improvements in the database engine, notifications services, replication and reporting services, according to an MSDN library Web page. SP3 contains all previously released cumulative updates for SQL Server 2005.

KnowledgeBase articles for SP3 are available through the release notes here.

For SQL users not opting for SP3, Microsoft released Cumulative Update 11 for SQL Server 2005 SP2, which contains all of the hot fixes for SP2, without the new features in SP3.

However for those who are moving from SQL Server SP2 to SP3, Microsoft offers a caveat. Be sure to apply SP3 Cumulative Update 1.

"If you are upgrading from SQL Server 2005 SP2 Cumulative Update 10 or from SQL Server 2005 SP2 Cumulative Update 11, you must apply a post-SP3 cumulative update after you upgrade to SP3 to obtain all the fixes," according to Nick MacKechnie's blog.

For those wanting more than just blog advice, Microsoft's "Books Online" release for Microsoft SQL Server 2005 is available here. It provides primary documentation, including setup and upgrade instructions for SP3.

Microsoft also released a new Feature Pack for SQL Server 2008 on Monday that provides optional add-ons for the database solution. The December Feature Pack can be accessed here.

For more information and links to documentation, visit the Swiss IT Professional and TechNet Blog.

About the Author

Herb Torrens is an award-winning freelance writer based in Southern California. He managed the MCSP program for a leading computer telephony integrator for more than five years and has worked with numerous solution providers including HP/Compaq, Nortel, and Microsoft in all forms of media.

Printable Format

comments powered by Disqus

Featured

Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.
Diving Deep into .NET MAUI

Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.
Copilot AI Boosts Abound in New VS Code v1.96

Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.
AdaBoost Regression Using C#

Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.
Versioning and Documenting ASP.NET Core Services

Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.