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 Query Store?


Query Store is the answer to the challenges described above. It collects the most relevant information about the executed queries: query text, parameters, query optimization and compilation details, execution plans, and execution statistics (execution time, CPU and memory usage, I/O execution details) and stores them in a database so that they are available after server restarts, failovers, or crashes.

You can use Query Store not only to identify performance issues, but also to fix some of them. Query Store offers a solution for issues caused by changed execution plans. By using Query Store, you can easily enforce the old plan; it is not required to rewrite the query or to write any code. You don't affect the business logic, therefore there is no need for testing, there is neither code deployment nor application restart. By taking this approach you can quickly implement a solution or at least a workaround, and save time and money.

Note

In addition to this, stored information...