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

Query Store use cases


Query Store is a very useful feature and can help you to identify and solve some performance problems, but also help you to learn about your workload and to be more familiar with it.

The main use cases are related to issues caused by a changed execution plan. Complex queries can have many potential execution plans and some of them can be performant, while some others lead to serious performance problems. The Query Optimizer does a great job when it generates execution plans but sometimes it comes up with a suboptimal plan. It is possible that two, totally different execution plans have similar costs. When a complex query has a good plan, the next plan for the same query can perform badly. The next plan might be generated when the old plan is not in the cache anymore. This happens when SQL Server is upgrading to a new version, when cumulative update or Service Pack is installed, when patching is performed, when a failover happens, and also when a new application or service...