2025-10-29
2025-10-29
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
5,139 reads
2022-10-26
432 reads
he SQL Server Database Engine processes queries on various data storage architectures such as local tables, partitioned tables, and tables distributed across multiple servers. The following sections cover how SQL Server processes queries and optimizes query reuse through execution plan caching.
2022-09-23
In this tip we look at how to save an execution plan for future review as well as using the full screen mode to see more of a query plan at one time.
2020-08-18
Starting to translate sp_BlitzCache into the cloud.
2018-07-27
4,046 reads
Brent demos a single query plan that asks for 2 identical indexes on the same table.
2017-12-26
3,142 reads
Rob Farley looks at information exposed in query plans about residual predicates and actual rows read, showing how Plan Explorer helps identify the issue.
2016-07-20
3,121 reads
SQL Server keeps the most-used execution plans in cache, so it doesn't need to recompile the same queries every time. How can we benefit from this to find potential performance problems in execution plans?
2015-01-13
9,693 reads
2011-10-27
2,276 reads
By Steve Jones
I wrote a piece on the new SUBSTRING in SQL Server 2025 and got...
By Steve Jones
If you aren’t watching the Ignite keynotes today, then you might have missed the...
Short version You want to get this running as fast as possible. Do these...
I changed my email address in Edit Profile page, but it has no effect...
Comments posted to this topic are about the item The case for "Understanding our...
Comments posted to this topic are about the item Specifying the Collation
I am dealing with issues on my SQL Server 2022 instance related to collation. I have an instance collation of Latin1_General_CS_AS_KS_WS, but a database collation of Latin1_General_CI_AS. I want to force a few queries to run with a specified collation by using code like this:
DECLARE @c VARCHAR(20) = 'Latin1_General_CI_AS'
SELECT p.PersonType,
p.Title,
p.LastName,
c.CustomerID,
c.AccountNumber
FROM Person.Person AS p
INNER JOIN Sales.Customer AS c
ON c.PersonID = p.BusinessEntityID
COLLATE @c
Will this solve my problem? See possible answers