It’s Friday, time to look back at the most popular RealSQLGuy posts of the week. Because it’s Friday and you’re not doing any real work anyway.
Posts That Were Popular This Week
- I’m Board
- What Are Your Servers Doing While You’re Sleeping?
- Don’t Bring a Tank to a Prison Fight – #TSQL2SDAY #49
- What’s In My Utility Belt? Issue #2
- Don’t Get Slimed By Bad Parameter Sniffing
- So, This Happened Today…
- CAST(‘RealSQLGuy’ AS BELIEVER)
- Using A Non-correlated Subquery To Avoid DISTINCT
- Automated Permissions Auditing With Powershell and T-SQL: Part 1
- Do You Need A Log Recovery Tool?
Comments That Were Posted This Week
- Andy on Using A Non-correlated Subquery To Avoid DISTINCT:
Great article! I cringe whenever I see “SELECT DISTINCT…”. To me it’s a red flag that somebody probably stuck a band-aid on their query because they didn’t understand why it was returning duplicates.
In your experience, does it make any performance difference if you use WHERE EXISTS versus WHERE IN, or do both techniques generate the same query plan? (I’d check myself, but something must be terribly wrong with me because I don’t have the AdventureWorks2012 database running anywhere!)
- realsqlguy on Using A Non-correlated Subquery To Avoid DISTINCT:
Thanks Andy. As far as I know, in almost every case, WHERE IN and WHERE EXISTS are processed in the same way by the query optimizer. The only difference is in how you construct the query.
- Robert L Davis on Don’t Bring a Tank to a Prison Fight – #TSQL2SDAY #49:
Thanks for your entry in T-SQL Tuesday #49.
- Paul Timmerman on I’m Board:
Congrats Tracy! I know you’ll do a great job. (wait, was I just nice to you??)
- realsqlguy on I’m Board:
I’m as shocked as you are…
This Week In History
None, the past holds no lessons this week
That’s it for this week. Get back to work!