News

Microsoft Releases SQL Server 2016 Service Pack 2

With a host of improvements based on customer and SQL community feedback, the SQL Server 2016 Service Pack 2 (SP2) was released by Microsoft.

Microsoft said the new release contains a roll-up of previously released hotfixes as well new and improved features focused on performance, scalability and supportability

The SP2 release is currently available through the Microsoft Download Center.

In addition to performance improvements and the addition of diagnostic functionality, SP2 includes all of the latest updates through SQL Server 2016 SP1 Cumulative Update 8. Microsoft had released SP1 back in late 2016.

It also includes Microsoft's Jan. 2 security update for speculative execution side-channel attack scenarios. For background, see the Redmond article by Microsoft Most Valuable Professional Joey D'Antoni.

In general, Microsoft improved database backup performance for "large memory machines" in SQL Server 2016 SP2. Performance also was enhanced by the addition of "backup compression support." Highlights on the performance side include:

  • An improved cleanup process for "oversized distribution database tables" to avoid "blocking or deadlock scenarios."
  • An improvement in "change tracking cleanup" for "Change Tracking side tables."
  • An I/O backup improvement that promises performance gains when "multiple small databases" are hosted on "large high-end servers with large memory."
  • VDI backup compression for Transparent Data Encryption-enabled databases.
  • Dynamic loading of Replication Agents parameters "without having to restart the agent."

On the diagnostics side, Microsoft improved the troubleshooting. It added improvements based on feedback from the last Microsoft Connect event. Highlights on the diagnostic side include:

  • Full support for "distributed transactions with Availability Group databases."
  • The closing of all Service Broker connections on Availability Group failovers.
  • A Dynamic Management Views addition for monitoring TempDB sizing "based on the version store usage requirements per database."
  • Ability to generate full dumps for Replication Agents for troubleshooting purposes.
  • Dynamic reloading of "some Replication Agent profile parameters" without having to restart the agent.

The full list of SQL Server 2016 SP2 improvements can be found in this Knowledge Base article.

Microsoft is recommending a reboot after installing SP2. While the service pack is currently available from the Microsoft Download Center, it'll be available "soon to Visual Studio subscriptions, MBS/Partner Source and VLSC [Volume Licensing Service Center]," Microsoft indicated.

About the Author

Kurt Mackie is senior news producer for 1105 Media's Converge360 group.

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.

Subscribe on YouTube