News

SQL Server 2008 SP4: Really, That's It This Time

The differences between this release and the SQL Server 2008 R2 SP3 release from last week are distinct enough to warrant separate releases.

As soon as we told you boldly that SQL Server 2008 R2 SP3 was the last update you'd see from Microsoft on this version of the DBMS, the company released SQL Server 2008 Service Pack 4. One might ask, why the two versions?

For a quick historical perspective, you'll have to go back a bit and recall the names "Kilimanjaro" and "Gemini." Kilimanjaro was the code name for the version of SQL Server that would contain a bevy of data warehousing capabilities. The original Microsoft release specifically highlighted Master Data Services, multi-server management capabilities, and scability coming from added support for 64 logical processors. Gemini referred to the development of self service business intelligence features that were also included at some point prior to the R2 release.

I asked Visual Studio Magazine frequent contributor Peter Vogel for some insight and he offered parallels to how Microsoft often maintains discrete development tracks for its operating systems. In this case, the specificity of features for the R2 release meant development had to be maintained separately from plain vanilla SQL Server 2008. "The patches are slightly different for each version of SQL Server so they have to be targeted to a specific version of SQL Server. However, because the different versions share a code base, the patches are similar in nature," he said.

Now that we have that straightened out, here are the basic facts on what's contained in SQL Server 2008 SP4:

  • It's a cumulative update of all the incremental issues and fixes for SQL Server 2008 SP3, with the inclusion of a last round of updates that are detailed" target="_blank">here.
  • There were 17 of them since the original SP3 release back in October 2011, if you're keeping track. They're all listed on a KB support page here.
  • Any updates moving forward will not include functional fixes (so says the blog).
  • There will be no more cumulative updates to these packages, but Microsoft will continue to provide security updates as needed and within the guidelines of its mainstream and extended support policies.

For details and download information on SQL Server 2008 R2 SP3, go here; for SQL Server 2008 SP4, go here.

About the Author

You Tell 'Em, Readers: If you've read this far, know that Michael Domingo, Visual Studio Magazine Editor in Chief, is here to serve you, dear readers, and wants to get you the information you so richly deserve. What news, content, topics, issues do you want to see covered in Visual Studio Magazine? He's listening at mdomingo@1105media.com.

comments powered by Disqus

Featured

  • Visual Studio Code Dev Team Cleans Up

    The Visual Studio Code development team focused on some housekeeping in the October update, closing more than 4,000 issues on GitHub, where the cross-platform, open-source editor lives.

  • ML.NET Model Builder Update Boosts Image Classification

    Microsoft announced an update to the Model Builder component of its ML.NET machine learning framework, boosting image classification and adding "try your model" functionality for predictions with sample input.

  • How to Do Naive Bayes with Numeric Data Using C#

    Dr. James McCaffrey of Microsoft Research uses a full code sample and screenshots to demonstrate how to create a naive Bayes classification system when the predictor values are numeric, using the C# language without any special code libraries.

  • Vortex

    Open Source 'Infrastructure-as-Code' SDK Adds .NET Core Support for Working with Azure

    Pulumi, known for its "Infrastructure-as-Code" cloud development tooling, has added support for .NET Core, letting .NET-centric developers use C#, F# and VB.NET to create, deploy, and manage Azure infrastructure.

  • .NET Framework Not Forgotten: Repair Tool Updated

    Even though Microsoft's development focus has shifted to the open-source, cross-platform .NET Core initiative -- with the aging, traditional, Windows-only .NET Framework relegated primarily to fixes and maintenance such as quality and reliability improvements -- the latter is still getting some other attention, as exemplified in a repair tool update.

.NET Insight

Sign up for our newsletter.

Terms and Privacy Policy consent

I agree to this site's Privacy Policy.

Upcoming Events