A bold statement that any SQL Server professional can stand behind with confidence. My development collogues and I are starting a regular blog series, outlining the vast range of scalability improvements, allowing SQL Server 2016 to run across a wide array of hardware configurations, faster and better than previous releases of SQL Server.
In the Sep 2014 the SQL Server CSS and Development teams performed a deep dive focused on scalability and performance when running on current and new hardware configurations. The SQL Server Development team tasked several individuals with scalability improvements and real world testing patterns. You can take advantage of this effort packaged in SQL Server 2016. -
“With our focused investment in performance and scale, simply upgrading to SQL 2016 could bring 25% performance improvement. SQL 2016 supports 3X more physical memory than previous versions. The new column store engine and query processing technology could increase query performance up to 100X and the new In-memory OLTP engine can process 1.25million batches/sec on a single 4 socket server, which is more than 3X of SQL 2014. “
- Rohan Kumar, Director of SQL Software Engineering
"SQL Server 2016 running on the same hardware as SQL Server 2014, 2012, 2008, 2008 R2 or 2005 uses fewer resources and executes a wide range of workloads faster. I have studied code check-ins and tested the improvements seeing the scalability improvement first hand and running SQL Server 2016 for internal SQL Support needs since Mar 2015 because of the improved features and scalability."
- Bob Dorr, Principle Engineer SQL Server Support
For example, by default SQL Server 2016 provides automatic, soft NUMA configuration. The following table is taken from an ASP.NET, session state cache, stress test.
Batch Requests / Sec
DBCC scales 7x better
Various spatial patterns execute 100s of times faster with specific paths up to 2000x faster
Multiple log writers
are just a few of the blogs we have slated.
Builds prior to the SQL Server 2016 release may require trace flags or configuration modifications to enable enhancements.
Bob Dorr - Principal SQL Server Escalation Engineer
Ryan Stonecipher - Principle SQL Server Software Engineer
I have received several inquiries about SKU applicability. While it is true that some features are SKU specific, these improvements were done in the engine so it could be leveraged by any SQL Server SKU. For example, the updated SOS_RWLock is simply a change to the synchronization primitive. Where SOS_RWLock is used, no matter the SKU, the new design applies.
Even when a change only appears in a specific feature today, it is still driving additional benefit discussions and improvements. For example, the improved compression capabilities applied to AlwaysOn are being tested and evaluated for use by the Backup/Restore code line.