Query Data Store (QDS)

The Basics - Level 1 of the Stairway to Query Store

  • Stairway Step

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 […]

5 (3)

2019-05-13

3,255 reads

Query Store and Parameterization Problems

  • Article

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

Query Store and In-Memory OLTP

  • Article

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

The SQL Server 2016 Query Store: Analyzing Query Store Performance

  • Article

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

The SQL Server 2016 Query Store: Built-in Reporting

  • Article

One of the most important features of the SQL Server 2016's new Query Store is the reporting. With these features, it is now possible to get a wealth of information on how your query workload is performing, either aggregated for the entire query workload or for a single query. With this information, you can see the effects of 'forcing' an execution plan for specific queries and get feedback of the consequences.

2016-03-03

3,901 reads

Blogs

Understanding Azure Geo-Redundant Storage

By

While at PASS Summit 2019, I gave a session on designing Azure Disaster Recovery...

Prompt in ADS

By

Ever since VS Code and Azure Data Studio came out, people have been asking...

When Too Much is Not a Good Thing

By

Explore how to avoid unwanted results that oft occur due to lack of attention...

Read the latest Blogs

Forums

Licencing Information

By Wecks

Hi Guys, I have the following question I am hoping that you guys can...

Countermeasure to stop forum spam bots

By jonas.gunnarsson 52434

There is a lot of spam from time to time. Is it possible to...

Query using fifo

By jsshivalik

Hi I have below Data . Using Fifo i want to display output Code...

Visit the forum

Ask SSC

SQL Server Q&A from the SQLServerCentral community

Get answers