In this article, we will learn how to interpret an execution plan of a SQL Server insert statement.

This article intends to give some details about the query optimization process in SQL Server.

In this article, we will talk about two query optimization myths and these myths can be changed according to the characteristics of the queries. Every query can exhibit different behaviors according to data distribution, SQL Server version, database settings, and other tons of parameters therefore the fixed ideas may not help to overcome the query performance issues. In the next part of the article, we will focus on the following most known discourse:

In this article, we will focus on how we can detect the parameter sniffing issues with different techniques.

In this article, we will learn what is plan regression and how we can fix this issue with help of the Automatic Plan Correction feature.

In this article, we will discuss how to read the SQL Server execution plan (query plan) with all aspects through an example, so we will gain some practical experience that helps to solve query performance issues. Interpreting query plans correctly is the first and major principle to troubleshoot query performance issues. When we try to find an answer to the “why is this query running slow?” question, the best starting point would be to analyze the query plan.

In this article, we will explore how the ORDER BY statement affects the query performance and we will also learn some performance tips related to sorting operations in SQL Server.