2025-05-05
442 reads
2025-05-05
442 reads
Introduction Instead of going straight into the topic of the Query Store, I would like to start this Stairway Series by mentioning a few performance tuning scenarios that are very common to production DBAs. I think most of us have been in one of these situations at some time: An application experiencing slowness after a […]
2020-10-07 (first published: 2019-05-13)
6,792 reads
Do you hate when someone wakes you up in the middle of the night and tells you that some query is slower and you need to investigate it? With SQL Server 2017 you might easily do this, or even let SQL Server do this job for you.
2017-08-08
1,997 reads
The query store gives us a novel way of identifying those queries that are causing performance problems when they are parameterized by SQL Server for reuse. Although it is relatively simple to ensure that certain troublesome queries avoid the problem, it is laborious to identify these queries. Additionally, Query Store gives us the means to fix the problem for groups of queries by means of plan guides without changing the DDL at all. Dennes Torres explains the details
2017-07-31
5,234 reads
2017-05-04
938 reads
Once you have Query Store enabled on your databases, runtime statistics are generated for your queries; but what about the natively-compiled stored procedures and memory optimised tables that come with In-Memory OLTP? Do you get the full range of runtime statistics? This is an intriguing question that Enrico explores and answers.
2017-03-07
4,670 reads
When you force a query plan via the Query Store, you will need to track what happens: Sometimes the request to force a plan will fail, and you will want to know when and why. There are several ways of getting feedback, ranging from the built-in reports to using extended events. Enrico explains the details.
2017-02-07
3,584 reads
Arshad Ali demonstrates how you can analyze the data collected by Query Store either with T-SQL scripting or with the graphical user interface in SSMS.
2016-10-20
4,404 reads
There are some obvious advantages to having the Query Store, but what is the performance impact that it is likely to have on a busy OLTP database server? It is early days, of course and until we get more experience we have to rely on Microsoft's estimate of a performance impact of 3-5% on average. However, this will depend on a number of factors such as usage an the way it is configured. Enrico explores some of these factors in order to give a clearer picture of what you should expect.
2016-05-13
3,339 reads
2016-04-08
1,184 reads
By Chris Yates
For decades, enterprises have approached data management with the same mindset as someone stuffing...
Truncate Table Pitfalls Truncating a table can be gloriously fast—and spectacularly dangerous when used carelessly....
You can find all the session materials for the presentation “Indexing for Dummies” that...
Comments posted to this topic are about the item DBCC CHECKIDENT
Comments posted to this topic are about the item Distributed Availability Group Health: T-SQL...
Hi, our peer who owns a remote mysql server from which we extract warehouse...
What is returned as a result set when I run this command without a new seed value?
See possible answers