As you might know, SQL Server uses internally Statistics to estimate how many rows are returned from a specific query. That process is called the Cardinality Estimation. Based on the output from the Cardinality Estimation the Query Optimizer generates an Execution Plan, which is cached and finally executed. In today’s blog posting I’m going to talk …
Today I’ve announced my SQLpassion Online Trainings for May 2017. On May 15 I’m doing again a free webcast from 11:00 – 12:00 (GMT + 1), where I will talk about how to Troubleshoot Latches in SQL Server. And on May 16 I’m running again a one-day long webinar about how to troubleshooting SQL Server …
Today I have published my 3rd Web Cast on YouTube. In this Web Cast I talk about Extended Events in SQL Server. Thanks for your time, -Klaus
The session option STATISTICS IO is my friend during query tuning engagements, because it tells you exactly how many page reads you had for a specific query. Every time that SQL Server requests a page of 8KB from the Buffer Pool, it gets logged through the output of STATISTICS IO. As a general guide I …
Do you need more than STATISTICS IO for Query Tuning? + read more
Today I want to talk more about Plan Caching and its side-effects in SQL Server. As you might know, every logical query submitted to SQL Server is compiled into a physical execution plan. That execution plan is afterwards cached in the so-called Plan Cache for further reuse. Let’s talk in the first step about adhoc SQL statements …
Be sure to checkout the FREE SQLpassion Performance Tuning Training Plan – you get a weekly email packed with all the essential knowledge you need to know about performance tuning on SQL Server.
