How It Works (It Just Runs Faster): Auto Soft NUMA…

Back in June, Bob Dorr gave you the thinking behind why SQL Server 2016 It Just Runs Faster due to changes in our SQL Server and NUMA configurations. Bob blogged about a new SQL Server 2016 feature called Auto Soft NUMA. As I’ve hit the road and talked more about SQL Server 2016: It Just…


How It Works (It Just Runs Faster): Non-Volatile Memory SQL Server Tail Of Log Caching on NVDIMM

Note: We received feedback that there was some confusion on us calling this functionality “tail of the log caching” because our documentation and prior history has referred to the tail of the log as the portion of the hardened log that has not been backed up. This feature is actually officially called Persisted Log Buffer…

7

SQL Server 2016 – It Just Runs Faster: Always On Availability Groups Turbocharged

When we released Always On Availability Groups in SQL Server 2012 as a new and powerful way to achieve high availability, hardware environments included NUMA machines with low-end multi-core processors and SATA and SAN drives for storage (some SSDs). Performance issues surrounding Availability Groups typically were related to disk I/O or network speeds. As we…


How It Works: Reader / Writer Synchronization

This post is not about a specific SQL Server object but instead outlines a technique used in various locations to reduce contention while still providing thread synchronization.  There are hundreds of locations throughout the SQL Server code base that must account for multi-threaded access.   A common technique used in multi-threaded coding is a reader, writer…

1

SQL 2016 – It Just Runs Faster Announcement

SQL Server 2016  ‘It Just Runs Faster’   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…

1

SQL 2016 – It Just Runs Faster: DBCC Scales 7x Better

Many of you have experienced (MULTI_OBJECT_SCANNER* based) waits while running DBCC CHECKS*(checkdb, checktable, …)   Internally DBCC CHECK* uses a page scanning coordinator design (MultiObjectScanner.)  SQL Server 2016 changes the internal design to (CheckScanner), applying no lock semantics and a design similar to those used with In-Memory Optimized (Hekaton) objects, allowing DBCC operations to scale…

3

SQL 2016 – It Just Runs Faster: DBCC Extended Checks

Last week’s post (SQL 2016 – It Just Runs Faster: DBCC Scales 7x Better) talked about several improvements to DBCC CHECKDB to make it run faster. In today’s post, we will talk about additional improvements to extended logical checks. When checking database consistency using DBCC CHECKDB, in addition to the amount of data or number…

0

SQL 2016 – It Just Runs Faster: Native Spatial Implementation(s)

Spatial data is among, if not the fastest, growing storage types for the SQL Server database.   It is common place for customers to have 3,000,000 or more rows in a database.   Customers are tracking vehicles, delivery locations, drilling positions and much more, leveraging the information to efficiently run their business.   To fully appreciate the…


SQL 2016 – It Just Runs Faster: TVPs with Spatial Column(s)

Table Valued Parameters (TVPs) containing spatial columns can be used as input parameter(s) to stored procedures.  SQL Server 2016 improves the scalability, using native spatial validation(s), increasing performance by 15 times or more.   TVP Before the Fix:  8000 rows/sec TVP After the Fix: 120,000 rows/sec   ‘It Just Runs Faster’ – Apply SQL Server…


SQL 2016 – It Just Runs Faster: Spatial Index Builds Faster

Index creation and tessellation are often intensive, spatial activities.    Along with the native and TVP, spatial enhancements additional work to optimize index creation and tessellation was completed.   Testing reveals that building a spatial index on SQL Server 2016, with the improved design, can be more than 2 times faster than SQL Server 2012 or…