To execute queries, the database engine of SQL Server analyzes the statement to find the most efficient way to access the required data. Analysis is done in the query optimizer. The input to the query optimizer comprises the query, the table and index definitions, and statistics. The output of the query optimizer is a query execution plan, sometimes referred to as a query plan or just an execution plan.
This session will go thru the history of execution plans as well as demos of using clustered, non-clustered and column-store indexes. After looking at the history, we will see where indexes are used and why they are not – sometimes. A separation of indexes in transitional (OLTP) databases will guide an attendee of the usefulness of a reporting system that uses more indexes than the OLTP system. The Query Store will be a repository of query plans and the dashboards/reports that can assist in performance tuning. Buckle up as we journey through being a better performance tuner in the SQL Server world.