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)

You rated this post out of 5. Change rating

2020-10-07 (first published: )

6,898 reads

External Article

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

External Article

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

External Article

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

Blogs

Building the Team: Roles and Responsibilities in FinOps

By

In my experience, FinOps success has never been just about tools or dashboards. It...

Tooling for Success: The Best FinOps Tools and Technologies

By

As a DevOps person, I know that to make FinOps successful, you need more...

From Planning to Practice: Setting Up Your FinOps Framework

By

As someone who works in DevOps, I’m always focused on creating systems that are...

Read the latest Blogs

Forums

Restoring On Top II

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Restoring On Top II

SQL Art 2: St Patrick’s Day in SSMS (Shamrock + Pint + Pixel Text)

By Terry Jago

Comments posted to this topic are about the item SQL Art 2: St Patrick’s...

Breaking Down Your Work

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Breaking Down Your Work

Visit the forum

Question of the Day

Restoring On Top II

I have a database, DNRTest, that has a number of tables and other objects in it. The other day, I was trying to mock up a test and ran this code on the same server:

-- run yesterday
CREATE DATABASE DNRTest2
GO
USE DNRTest2
GO
CREATE TABLE NewTable (id INT)
GO
Today, I realize that I need a copy of DNRTest for another mockup, and I run this:
-- run today
USE Master
BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak'
GO
RESTORE DATABASE DNRTest2 FROM DISK = 'dnrtest.bak' WITH REPLACE
What happens?

See possible answers