2011-09-20
2,437 reads
Query plans
2011-06-28
2,673 reads
Showplan Operator of the Week – SORT
Fabiano introduces another ShowPlan operator that is used to build a query plan, or perform an operation specified in the DML. Once again, Fabiano demonstrates why it is important to be aware of these operators when getting queries to perform well.
2010-11-03
2,705 reads
DMVs for Query Plan Metadata
Before you can tackle any performance issues with a working database, you need to know which queries to work on first: The ones that are taking the most time in total, and which are the most expensive in terms of cache, CPU and disk. Although SQL Server Management Studio can help, it isn't long before you need an armoury of DMVs to provide you the statistics to find the culprits.
2010-09-02
3,298 reads
Queries, Plans, and Indexes
Find indexes associated with queries and vice versa. Helps figure out what procedures are using indexes.
2008-11-18 (first published: 2008-07-31)
1,722 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