Parameter Sensitive Plan Optimization in SQL Server 2022
Learn about a new feature of SQL Server 2022 - Parameter Sensitive Plan Optimization(PSPO)
2025-09-15
2,038 reads
query plan
Optimized Plan Forcing with Query Store in SQL Server 2022
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,812 reads
Identifying and Solving Index Scan Problems
When you're developing database applications, it pays to check for index scans in the SQL Server query plan cache. Once you've identified the queries, what next? Dennes Torres gives some preliminary guidelines on how to find out why these index scans are being chosen for these queries and how to make the queries run faster and more efficiently.
2015-03-30
9,858 reads
Blogs
The SUM of Nothing: #SQLNewBlogger
By Steve Jones
I caught this interesting item over on Pinal Dave’s blog: Eleven Interview Questions that...
How to Move the SSMS Status Bar to the Top and Color-Code SQL Server Connections
By Hemantgiri
I use color-coded connections in SSMS to distinguish Production, Pre-Production, UAT, and Development. But...
Architecting Zero Downtime Deployments–Day of Data Boston
By Steve Jones
Here are the resources for my talk at Day of Data Boston. Slides –...
Forums
Split Large Queries in Athena with a Simple Modulo Trick
Comments posted to this topic are about the item Split Large Queries in Athena...
Finding Trailing Spaces
Comments posted to this topic are about the item Finding Trailing Spaces
Question of the Day
Finding Trailing Spaces
I have some data in a SQL Server 2025 database. It looks like this for the dbo.Customer table:
CustomerID CustomerName PreferredName 1 Steve Steve 2 Andy Andy 3 Brian Brian 4 Allan Allan 5 Devin Devin 6 Steve Steve 7 Sally SallyI want to detect which names have a single trailing space. The CustomerName is a varchar() and the PreferredName is a CHAR(). Does this query detect the problem rows?
SELECT
CustomerID,
CustomerName,
PreferredName
FROM Customer
WHERE CustomerName <> RTRIM(CustomerName)
OR PreferredName <> RTRIM(PreferredName); See possible answers