Query plan hash
This is post 3 in the series about query fingerprints. Here’s the previous posts in this series:
Query HashSQL Handle
What is...
2019-01-07
301 reads
This is post 3 in the series about query fingerprints. Here’s the previous posts in this series:
Query HashSQL Handle
What is...
2019-01-07
301 reads
I like public speaking, but I haven’t always liked it. It started when I read Dale Carnegie’s book on public...
2019-01-05
33 reads
Let’s talk about how queries use memory, specifically in the execution plan. One of the query operators that use memory...
2019-01-04
132 reads
If you’re on SQL Server 2016 or above, maybe you’re thinking about using the Query Store. That’s good! It’s an...
2019-01-03
879 reads
I know this post might sound obvious. This is a very rare problem. But this actually happened to me, and...
2019-01-02
34 reads
By Steve Jones
I love Chicago. I went to visit three times in 2023: a Redgate event,...
By Brian Kelley
I have found that non-functional requirements (NFRs) can be hard to define for a...
You can find the slidedeck for my Techorama session “Microsoft Fabric for Dummies” on...
I have had a hard time to understand how to use EXISTS. I Always...
Dears, We are using Azure Data factory pipes to run some stored procedures against...
Hi, I have SQL Server 2019 installed and when go the Clear Trace database...
Let’s consider the following script that can be executed without any error on both SQL Sever and PostgreSQL. We define the table t1 in which we insert three records:
create table t1 (id int primary key, city varchar(50)); insert into t1 values (1, 'Rome'), (2, 'New York'), (3, NULL);If we execute the following query, how will the records be sorted in both environments?
select city from t1 order by city;See possible answers