Cardinality Estimation for a Predicate on a COUNT Expression
Paul White takes you on an optimizer journey, exploring how SQL Server comes up with cardinality estimates for COUNT queries.
2017-05-17
3,222 reads
Paul White takes you on an optimizer journey, exploring how SQL Server comes up with cardinality estimates for COUNT queries.
2017-05-17
3,222 reads
Aaron Bertrand shares some insight about early changes to Plan Explorer that help to provide you with the most accurate information we can.
2016-04-04
2,780 reads
The Query Optimiser needs a good estimate of the number of rows likely to be returned by each physical operator in order to select the best query plan from the most likely alternatives. Sometimes these estimates can go so wildly wrong as to result in a very slow query. Joe Sack shows how it can happen with SQL Queries on a data warehouse with a star schema.
2012-12-10
1,163 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...
Testing with AG on Linux with Cluster=NONE. it was all going ok and as...
Hi, I have two tables: one for headers with 9 fields and another for...
We're trying to understand how quick new versions of SQL server can be. Obviously...
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