Book Image

SQL Server 2016 Developer's Guide

By : Miloš Radivojević, Dejan Sarka, William Durkin
Book Image

SQL Server 2016 Developer's Guide

By: Miloš Radivojević, Dejan Sarka, William Durkin

Overview of this book

Microsoft SQL Server 2016 is considered the biggest leap in the data platform history of the Microsoft, in the ongoing era of Big Data and data science. This book introduces you to the new features of SQL Server 2016 that will open a completely new set of possibilities for you as a developer. It prepares you for the more advanced topics by starting with a quick introduction to SQL Server 2016's new features and a recapitulation of the possibilities you may have already explored with previous versions of SQL Server. The next part introduces you to small delights in the Transact-SQL language and then switches to a completely new technology inside SQL Server - JSON support. We also take a look at the Stretch database, security enhancements, and temporal tables. The last chapters concentrate on implementing advanced topics, including Query Store, column store indexes, and In-Memory OLTP. You will finally be introduced to R and learn how to use the R language with Transact-SQL for data exploration and analysis. By the end of this book, you will have the required information to design efficient, high-performance database applications without any hassle.
Table of Contents (21 chapters)
SQL Server 2016 Developer's Guide
Credits
About the Authors
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface
12
In-Memory OLTP Improvements in SQL Server 2016

What is missing in SQL Server 2016?


SQL Server 2016 is the first SQL Server version that has some built-in support for temporal data. However, the support is still quite basic. SQL Server 2016 supports system-versioned tables only. You saw at the beginning of this chapter that application-versioned tables, and of course bitemporal tables, add much more to the complexity of temporal problems. Unfortunately, in order to deal with application validity times, you need to develop your own solution, including your own implementation of all the constraints you need to enforce data integrity. In addition, you need to deal with the optimization of temporal queries by yourself as well.

It would also be nice if you were able to define the retention period for the historical rows, like you can define for the Query Store. Currently, you have to do the history data cleanup by yourself.

If you are familiar with analytical applications and data warehouses, you might think that system-versioned temporal tables...