Don’t use DISTINCT as a “join-fixer”
I’ve quietly resolved performance issues by re-writing slow queries to avoid DISTINCT. Often, the DISTINCT is there only to serve as a “join-fixer,” and I can explain what that means using an example.
2023-11-06
DISTINCT
2020-09-22
908 reads
2011-02-08
28,216 reads
Blogs
Why your data still can’t answer a simple question
Every organization I talk to has the same problem dressed up in different clothes....
T-SQL Tuesday #197 Invitation – An impactful session or two from a conference
By DataOnWheels
I am delighted to host this month’s T-SQL Tuesday invitation. If you are new...
Did You Really Name That Default?
By alevyinroc
Ten years (and a couple jobs) ago, I wrote about naming default constraints to...
Forums
The day-to-day pressures of a DBA team, and how we can work smarter with automation and AI
Comments posted to this topic are about the item The day-to-day pressures of a...
CMS server query & temp tables
I am annoyed. We have a CMS server that has hundreds of servers saved...
The Problem Isn't Always Your Query or Schema... Sometimes It's Hidden Assumptions
Comments posted to this topic are about the item The Problem Isn't Always Your...
Question of the Day
Identity Defaults
What happens when I run this code?
CREATE TABLE dbo.IdentityTest
(
id int IDENTITY(10) PRIMARY KEY,
somevalue VARCHAR(20)
)
GO
See possible answers