Life Cycle of a Query
- The command parser evaluates the query and generates a hash to see if the buffer pool has an execution plan already stored.
- The buffer pool maintains the execution plan cache (via a hash to identify each plan cached), and a the data cache.
- Creating execution plans can be time consuming and resource intensive. Which is why SQL Server checks the cache first for a plan.
- If no plan is found in the cache, the command parser generates a query tree based on the SQL.
- The query tree is then passed to the Query Optimizer where an execution plan is created.[1. The query optimizer evaluates multiple ways to execute the query when creating the plan. The Query Optimizer does not always pick the BEST plan but a good plan in a reasonable amount of time]
- *The Query Optimizer has its own Rules Processor to examine the query. Query Optimizer go thru multiple stages for generating a good acceptable plan
- *Stage 1 (Pre Optimization Stage): possibility of TRIVIAL PLAN
- *Stage 2 (Simple to Full optimization stages) will generate and evaluate many plans and will choose plan with LOWEST COST
- Execution plan is stored in Plan cache for reuse and passed to Query Executor
- Query Executor checks PAGE availability in DATA CACHE. If not available PAGE is retrieved from Disk
(System pages (like GAM, SGAM, IAM) and Index pages etc are used to manage, identify pages quicker)
- Result set is formatted as relational table (as XML if FOR XML is specified) and encapsulated in TDS packet
- Server side SNI encapsulates the TDS (Tabular Data Stream) packet inside a standard communication protocol, such as TCP/IP or named pipes and move it to the client
- Client SNI receives the TDS packet (Default port 1433), unpack the result set and show it in Grid
Here are some database level factors that influence query performance:
- Usable Index
- Sargable arguments
- Database configurations
- Query Hints
* SQL Servers uses write-ahead logging to maintain durability
* Data modifications are written to the log first, then to memory only. This is done for performance reasons and enables you to recover changes form the transaction log if necessary
* When data is read from disk to memory (cache), it is considered to be a “clean” page
* A dirty page is a page in memory that has been updated but not persisted back to disk
* You can use the following to see the number of dirty pages per database:
SELECT DB_NAME(database_id) AS 'Database'
,COUNT(page_id) AS 'Dirty Pages'
WHERE is_modified = 1
GROUP BY DB_NAME(database_id)
ORDER BY COUNT(page_id) DESC
* The dirty pages will be written periodically to disk when the “free buffer” list is low or a checkpoint occurs
* The Lazy Writer is a thread that periodically checks the size of the Free Buffer List and when it is low, ages-out the oldest pages, which causes them to be written back to disk
* The Checkpoint process ensures that all “committed” transactions written to the transaction log are written to disk (hence no dirty pages in memory)
The Lazy Writer process
Periodically checks the size of the Free Buffer List and, when it is low of memory, will do the following:
*Monitors free memory on the server and will do the following:
The Checkpoint Process
A checkpoint is a point in time created by the checkpoint process at which SQL Server can be sure that any committed transactions have had all their changes written to disk. This checkpoint then becomes the marker from which database recovery can start.
The checkpoint process ensures that any dirty pages associated with a committed transaction will be flushed to disk. It can also flush uncommitted dirty pages to disk to make efficient use of writes but unlike the lazy writer, a checkpoint does not remove the page from cache; it ensures the dirty page is written to disk and then marks the cached paged as clean in the page header.
By default, on a busy server, SQL Server will issue a checkpoint roughly every minute, which is marked in the transaction log. If the SQL Server instance or the database is restarted, then the recovery process reading the log knows that it doesn’t need to do anything with log records prior to the checkpoint.
Views – 614