A common criticism for SQL Server’s security model is that it only understands tables and columns. If you want to apply security rules on a row-by-row basis, you have to simulate it using stored procedures or table value functions, and then find a way to make sure there is no way to bypass them. With SQL Server 2016, that is no longer a problem.
SQL Server 2016 seeks to make encryption easier via its new Always Encrypted feature. This feature offers a way to ensure that the database never sees unencrypted values without the need to rewrite the application.
SQL Server 2016’s new Temporal Table feature makes it easy to work with data that needs to be versioned.
SQL Server 2016’s new stretch database feature promises to offer local server performance for hot data and cloud storage for old data without any change to the application.
In SQL Server 2014 we saw the introduction of Natively Compiled Stored Procedures. In 2016 we’ll be able to do the same for Scalar User Defined Functions.
Memory Optimized Tables promise significant performance gains, but tend to be difficult to work with. SQL Server 2016 reduces much of the pain by offering ALTER TABLE support.
Clustered Columnstore Indexes were one of the two headline features for SQL Server 2014. Designed for tables with over 10 million rows, they allow for good performance on analytical queries without the need to explicitly specify indexes. With SQL Server 2016, they gain the ability to support secondary indexes.
Non-clustered Columnstore Indexes are also getting some enhancements in SQL Server 2016. The most notable of these enhancements is the ability to be updated.
New for SQL Server 2016 is the ability to place a Columnstore Index on an In-Memory Table.
SQL Server 2016 will finally see native support for JSON.
A lot of small releases were made by Microsoft’s SQL Server team last month. Some of the highlights include Power BI for on-site servers, System Center support for SQL Server 2014, and updated Java/PHP drivers.
In their latest Patch Tuesday, Microsoft issued 9 bulletins covering a total of 37 common vulnerabilities and exposures (CVE) spread across some of their products.
The second service pack for SQL Server 2012 was recently released with over 30 bug fixes since the last cumulative update. But according to Aaron Bertrand of SQL Sentry, one important hotfix for Enterprise customers didn’t make the cut.
SQL Server has been released to manufacturing with general availability set for April 1st. Through this week we’ll be covering various aspects of the new release starting with data warehousing.
Indexes in SQL Server’s In-Memory OLTP don’t work exactly like normal indexes. This isn’t necessarily a bad thing, but the differences need to be kept in mind to avoid performance problems.