In this Article , We will delve into the world of Query Store and explore how to use Optimized Plan Forcing to improve performance in SQL Server 2022. We will discuss what it is, how it works, and how it can impact your system's performance.
2023-09-04
2,912 reads
A good example where the Query optimizer picks the wrong query plan and suggested index.
2021-02-25
4,543 reads
Want to 'trick' SQL Server into performing millions of logical reads to return data, when only are few thousand were really required? In this article, Gail Shaw examines three common forms of generic SQL that can and will confuse the SQL Server Optimizer to the point that it generates and reuses very inefficient execution plans.
2015-09-21
3,875 reads
SQL Server Query Optimizer uses statistical information to estimate the cardinality in a query result. This enables the SQL Server Query Optimizer to create a high-quality query execution plan. Read on to learn how to use statistics and why it’s needed.
2015-01-07
8,382 reads
2013-09-19
2,856 reads
In this article, you will learn what query optimisation statistics are and how SQL Server query optimizer uses statistics. You will also learn how to create and manage statistics, and what are the different ways to determine when statistics were last updated in SQL Server.
2013-07-10
4,410 reads
To understand how to write SQL code for SQL Server that performs well, it is important to appreciate how the query optimizer works. Ben Nevarez explains the essentials, in a broad sweep through a complex subject, in an article taken from his new book 'Inside the SQL Server Query Optimizer'.
2011-09-09
4,876 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