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.
Opserver is an open source monitoring solution, released by StackExchange, of StackOverflow's fame. Opserver provides a quick overall view of each monitored system's health, while allowing the user to deep dive using a drill-down approach. InfoQ talked with Nick Crave, one of Opserver’s creators, for additional insight.
One of the biggest challenges when researching a new technology is determining where to start. A typical SQL Server installation could easily have hundreds of tables. Examining each one by hand to determine which would benefit from conversion, is a daunting challenge. This is where the AMR Tool comes into play.
In this report we look at the internals of SQL Server’s In-Memory OLTP to see how it uses timestamp-like transaction ids in lieu of locks.
SQL Server 2014 will offer Clustered Columnstore Indexes. These will offer the performance and compression benefits of column-oriented storage without the need to restrict the underlying table to read-only access.
Originally this report was titled “Natively Compiled Queries”, but that doesn’t do justice to how deep this runs. When a memory optimized table is created, SQL Server will create a DLL specifically for that table. All data access for the table, including indexes, occurs through this DLL.
SQL Server 2014’s Memory Optimized Tables handle indexes very differently than traditional tables. First and foremost, you must have at least one index and cannot have more than eight indexes. Only the primary key can be marked as unique and don’t even think about foreign keys or filtered indexes.