Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit 2aa18e5

Browse files
Added link.
1 parent 940c269 commit 2aa18e5

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

‎docs/findings/SQLCodeDevelopment.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1364,6 +1364,8 @@ So, while DISTINCT and GROUP BY are identical in a lot of scenarios, there is on
13641364

13651365
You also might be using SELECT DISTINCT to mask a JOIN problem. It’s much better to determine why rows are being duplicated and fix the problem.
13661366

1367+
- See: [Performance Surprises and Assumptions : GROUP BY vs. DISTINCT](https://sqlperformance.com/2017/01/t-sql-queries/surprises-assumptions-group-by-distinct) by Aaron Bertrand
1368+
13671369
[Back to top](#top)
13681370

13691371
---

0 commit comments

Comments
(0)

AltStyle によって変換されたページ (->オリジナル) /