Using Query Store to Identify CPU Intensive SQL Queries and Creating Proper Indexes
Learn how to use SQL Server Query Store to identify what resources are using CPU to help fine-tune queries and reduce the processing load.
2024-07-22
Learn how to use SQL Server Query Store to identify what resources are using CPU to help fine-tune queries and reduce the processing load.
2024-07-22
2024-07-17
315 reads
2024-01-29
395 reads
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
2023-04-28
325 reads
2023-02-20
454 reads
2020-12-28
529 reads
2020-11-20
624 reads
2020-02-13
586 reads
Erik Darling loves query store, but he really hates the default capture mode.
2019-01-25
2,931 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