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,498 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

Custom deployment parameters in Azure Data Factory - Forget Me Not

By

(2020-Sep-26) Last week one of my Azure Data Factory (ADF) deployment pipelines failed with an...

VMworld 2020 – Top 10 Database Sessions (Part 2)

By

Whether you are a SQL Server Database Administrator, Infrastructure Architect, or any other member...

Daily Coping 25 Sep 2020

By

I started to add a daily coping tip to the SQLServerCentral newsletter and to...

Read the latest Blogs

Forums

Report Server Load balanced issue with one server while accessing https:

By PJ_SQL

We have 2 servers which are load balanced, when reporting service is stopped on...

multipoint to line geometry

By lpro

Hi, Attached, I exported a CSV file from a multipoint record from sql server ...

Using SSIS packages build in VS2010 when migrating SQL server from 2008 to 2016

By blom0344

With eof of Windows2008R2, lots of our customers are planning new server setups, usually...

Visit the forum

Ask SSC

SQL Server Q&A from the SQLServerCentral community

Get answers