Search icon CANCEL
Subscription
0
Cart icon
Cart
Close icon
You have no products in your basket yet
Save more on your purchases!
Savings automatically calculated. No voucher code required
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
SQL Server 2016 Developer's Guide

You're reading from  SQL Server 2016 Developer's Guide

Product type Book
Published in Mar 2017
Publisher Packt
ISBN-13 9781786465344
Pages 616 pages
Edition 1st Edition
Languages
Authors (3):
Miloš Radivojević Miloš Radivojević
Profile icon Miloš Radivojević
Dejan Sarka Dejan Sarka
Profile icon Dejan Sarka
William Durkin William Durkin
Profile icon William Durkin
View More author details
Toc

Table of Contents (21) Chapters close

SQL Server 2016 Developer's Guide
Credits
About the Authors
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface
1. Introduction to SQL Server 2016 2. Review of SQL Server Features for Developers 3. SQL Server Tools 4. Transact-SQL Enhancements 5. JSON Support in SQL Server 6. Stretch Database 7. Temporal Tables 8. Tightening the Security 9. Query Store 10. Columnstore Indexes 11. Introducing SQL Server In-Memory OLTP 12. In-Memory OLTP Improvements in SQL Server 2016 13. Supporting R in SQL Server 14. Data Exploration and Predictive Modeling with R in SQL Server

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...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at ₹800/month. Cancel anytime