I am working with clients on helping them tune their SQL Server Performance. Let us learn how we can use SET STATISTICS IO to check the query’s performance.
FORCE_DEFAULT_CARDINALITY_ESTIMATION: A Simple Explanation
FORCE_DEFAULT_CARDINALITY_ESTIMATION is a query hint that gives one query the default cardinality estimator, even when the database is set to the legacy one. This post builds a demo table, compares the row estimates of both models with the real count and shows how to prove which model a plan used. It also names the opposite hint and the permission difference.
Full-Screen Execution Plan – SQL in Sixty Seconds #117
There are two primary tools – 1) Execution Plan and 2) Statistics IO. In this blog post, we will see how we can get the full-screen execution plan.
Watch a Running Query: Live Plan From Activity Monitor
To watch a running query, open Activity Monitor in SSMS 22, find the query in Active Expensive Queries, and open its live execution plan. It also shows the settings that older versions need and a T-SQL query that reads the same facts.
Email an Execution Plan – SQL in Sixty Seconds #114
Today we are going to learn how we can send Email an Execution Plan. In the video, I explain how one can send query plans via an email.
Execution Plan – Estimated vs Actual – SQL in Sixty Seconds #113
During the Comprehensive Database Performance Health Check, I often get the question about Estimated vs Actual Execution Plan. Let’s discuss.
Single Column Single Row and TABLE SCAN – SQL in Sixty Seconds #111
Can a single column and single row result do an entire table scan? I recently got this question in my Comprehensive Database Performance Health Check.