Statistics and the Ascending Key Problem
I’ve mentioned previously how not having up to date statistics can cause problems in query performance. This post looks at something called the Ascending Key Problem which can badly...
2021-02-09
184 reads
I’ve mentioned previously how not having up to date statistics can cause problems in query performance. This post looks at something called the Ascending Key Problem which can badly...
2021-02-09
184 reads
Statistics are vitally important in allowing SQL Server to find the most efficient way to execute your queries. In this post we learn more about them, what they are...
2021-03-24 (first published: 2021-02-01)
401 reads
When you don't have statistics, what does SQL use to calculate the estimated number of rows?
2021-02-04 (first published: 2021-01-26)
296 reads
Statistics objects are important for allowing the SQL Server Optimizer to make good estimates and form efficient execution plans. Related to that it's useful for us to understand when...
2021-01-25 (first published: 2021-01-18)
502 reads
Query Store is a configuration that is enabled per database, and the plans and stats for queries executed in that database are stored in the database itself. So what...
2021-01-18 (first published: 2021-01-11)
472 reads
Script to identify the most expensive queries on your database server using the Query Store DMVs. This allows you to look at data from a specific time frame, as...
2021-01-11 (first published: 2021-01-04)
695 reads
Here's a SQL Puzzle for the festive period. 2020 has been a year of many things but amongst it all, it has been the year of chess. The combined...
2020-12-24 (first published: 2020-12-15)
537 reads
Introduced with SQL 2016, Query Store was, probably without doubt, the most anticipated and talked out new feature. In this post we'll just take a brief look at it,...
2020-12-21 (first published: 2020-12-14)
934 reads
Recently Microsoft quietly let us know that TDE (Transparent Data Encryption) will be available in the Standard Edition of SQL Server 2019. If you don’t follow SQL topics on...
2019-11-12 (first published: 2019-11-05)
7,126 reads
No, the answer isn’t because you’re a DBA. This isn’t a technical post about databases, but rather a discussion of a statistical paradox that I read about recently. Statistics...
2019-10-01
40 reads
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
Comments posted to this topic are about the item Restoring On Top II
Comments posted to this topic are about the item SQL Art 2: St Patrick’s...
Comments posted to this topic are about the item Breaking Down Your Work
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) GOToday, 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 REPLACEWhat happens? See possible answers