Upgrade To 2016?

Kendra Little explains why upgrading to 2016 is a good idea:

I know most of y’all care about Standard Edition.

With SP1, you can use all sorts of (formerly) super-expensive features like data compression, partitioning, Columnstore, Change Data Capture, Polybase, and more in Standard Edition.

A few features have scalability caps in “lower” editions. There’s a memory limit for In-Memory OLTP (aka Hekaton), and Columnstore. Columnstore also has restrictions on parallelism.

I’ll also throw out my experience as an anecdote:  2016 has been more stable than 2014 in our environment.  I don’t regret going to 2014, but we’re better off on 2016.

Related Posts

Running SQL Server 2019 In A Docker Container

Cathrine Wilhelmsen shows us how to set up a Docker container running SQL Server 2019 on Linux: In this post, I share my approach and code snippets for: Installing Docker Getting SQL Server 2019 Running SQL Server 2019 in a Docker Container Restoring Demo Databases (AdventureWorks and WideWorldImporters) If your hardware supports Docker, this is […]

Read More

Join Estimation: Details On A Cardinality Estimator Change

Paul White shares some detail on a change to the Cardinality Estimator in SQL Server 2014: The question is now how to perform a coarse estimation of the equijoin cardinality of the highlighted steps, using the information available. The original cardinality estimator would have performed a fine-grained step-by-step histogram alignment using linear interpolation, assessed the join contribution […]

Read More

Categories

November 2016
MTWTFSS
« Oct Dec »
 123456
78910111213
14151617181920
21222324252627
282930