I had earlier written, interesting article series on the limitations of the views. I had a great time writing this series. I got many many requests.
NO_PERFORMANCE_SPOOL: Compare the Work Before Keeping the Hint
NO_PERFORMANCE_SPOOL changes one query optimization decision. A guarded private fixture compares baseline work, the optional hint and a supporting inner index. The article explains how to preserve results and assess actual child work without promising a plan shape.
SQL SERVER – Get Query Running in Session
I forgot the simple syntax to get query running in session and ended up on my own old post. Here is the one method I use most during performance tuning.
What a Cumulative Update Actually Contains
Understand a SQL Server cumulative update, identify your build and servicing branch, and read fixes and known issues before planning a patch.
Shredding sp_server_diagnostics Output Into Health Rows
Check shredding sp_server_diagnostics with SQL Server examples, practical queries, clear limits, and steps to verify your own database.
SQL SERVER – View Over the View Not Possible with Index View – Limitations of the View 11
Why can’t you create a view over the view and index it? An index view cannot reference another view. Limitation of the view 11 shows an example.
Wait Statistics: Read the Snapshot Before Naming the Bottleneck
Wait statistics provide a starting point for investigation. Separate cumulative completed waits, background activity, signal time and currently waiting requests before treating the largest total as the present bottleneck.