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

Use cases for Stretch Database


With so many limitations, finding use cases for Stretch DB does not seem to be an easy task. You would need tables without constraints and rare data types that are not involved in relations with other tables and that don't use some special SQL Server features. Where to find them? As potential candidates for stretching, you should consider historical or auditing and logging tables.

Archiving of historical data

Historical or auditing data is commonly produced automatically by database systems and does not require constraints to guarantee data integrity. In addition to this, it is usually in large data sets. Therefore, historical and auditing data can be a candidate for using the Stretch DB feature. SQL Server 2016 introduced support for system-versioned temporal tables. They are implemented as a pair of tables: a current and a historical table. One of the requirements for historical tables is that they cannot have any constraints. Therefore, historical tables used...