I enjoy working on SQL Server Performance challenges and every day I learn something new. Recently one of the clients asked me Comprehensive Database Performance Health Check if they can change the join hints to improve the performance of the query. Well, the reality is that I always Avoid Join Hints.
A very common thought is that SQL Server Optimizer needs human guidance and honestly, I believe it is not true. SQL Server optimizer has come a long way from its initial version and most of the time makes the right decision for the query. Let us watch a video today which gives you a practical example of Avoid Join Hints.
Here is the video where I describe why I like to Avoid Join Hints:
Here is the link to the blog post containing the script used in the video: SQL SERVER – Change Join Type for Query. Well, that’s it for today. If you liked this video, please do not forget to subscribe to my YouTube Channel – SQL in Sixty Seconds.
Here are my few recent videos and I would like to know what is your feedback about them.
- One Query Many Plans – SQL in Sixty Seconds #171
- Best Value for Maximum Worker Threads – SQL in Sixty Seconds #170
- Copy Database – SQL in Sixty Seconds #169
- 9 SQL SERVER Performance Tuning Tips – SQL in Sixty Seconds #168
- Excel – Sum vs SubTotal – SQL in Sixty Seconds #167
- 3 Ways to Configure MAXDOP – SQL in Sixty Seconds #166
- Get Memory Details – SQL in Sixty Seconds #165
- Get CPU Details – SQL in Sixty Seconds #164
- Shutdown SQL Server Via T-SQL – SQL in Sixty Seconds #163
- SQL Server on Linux – SQL in Sixty Seconds 162
- Query Ignoring CPU Threads – SQL in Sixty Seconds 161
- Bitwise Puzzle – SQL in Sixty Seconds 160
- Find Expensive Queries – SQL in Sixty Seconds #159
- Case-Sensitive Search – SQL in Sixty Seconds #158
- Wait Stats for Performance – SQL in Sixty Seconds #157
- Multiple Backup Copies Stripped – SQL in Sixty Seconds #156
Reference: Pinal Dave (http://blog.SQLAuthority.com)