CHECKPOINT impact on memory is easy to measure. This post counts the dirty and clean pages of one database before and after a checkpoint. Dirty pages drop to zero, the clean pages grow by the same amount, and nothing leaves memory.
Dirty Pages and Clean Pages in the SQL Server Buffer Pool
Dirty pages are pages in memory that SQL Server has changed but not yet written to the data file. This post counts dirty pages and clean pages per database and per object, then watches a CHECKPOINT bring the dirty count to zero. It also explains why you should not try to clean the buffer pool on a production server.
How Much Memory is in Locked Pages? – Interview Question of the Week #228
Question: How Much Memory is in Locked Pages? Answer: Before we see the answer to this question, I suggest you read the blog post here first.
How to List All Memory Optimized Tables in SQL Server? – Interview Question of the Week #227
Question: How to List All Memory Optimized Tables in SQL Server? We will see two different scripts here: One for Database and Second for Tables.
Plan Cache Memory by Cache Store: Where Plans Use Your RAM
Break down plan cache memory by cache store and object type, compare memory clerks, and investigate unused plans without cache clearing.
When was Table Accessed Last By User? – Interview Question of the Week #226
When was a table accessed last by a user? When clients say a table is rarely used, I run this report to check before we create or drop indexes.
When Was SQL Server Last Restarted? – Interview Question of the Week #225
When was SQL Server last restarted? It is my first question in every Health Check, because a restart empties the DMVs and their performance history.