<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Page Life Expectancy on SQL Server Scripts</title><link>https://www.sqlserver70.com/tags/page-life-expectancy/</link><description>Recent content in Page Life Expectancy on SQL Server Scripts</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>SQLServer70.com</copyright><lastBuildDate>Sun, 06 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.sqlserver70.com/tags/page-life-expectancy/index.xml" rel="self" type="application/rss+xml"/><item><title>Decode PLE and Buffer Cache Hit Ratio via cntr_type Codes</title><link>https://www.sqlserver70.com/post/page-life-expectancy-dm-os-performance-counters/</link><pubDate>Sun, 06 Sep 2026 00:00:00 +0000</pubDate><guid>https://www.sqlserver70.com/post/page-life-expectancy-dm-os-performance-counters/</guid><description>
&lt;p&gt;How many seconds should a data page sit in the buffer pool before &lt;a href="https://learn.microsoft.com/en-us/sql/sql-server/"&gt;SQL Server&lt;/a&gt; decides it isn't needed anymore, and where does that number actually come from? Page life expectancy is one row among hundreds returned by &lt;a href="https://learn.microsoft.com/en-us/sql/relational-databases/system-dynamic-management-objects/sys-dm-os-performance-counters-transact-sql?view=sql-server-ver17"&gt;sys.dm_os_performance_counters&lt;/a&gt;, and reading it correctly — along with its neighbor, buffer cache hit ratio — depends entirely on a column most ad hoc queries against this view skip past: &lt;code&gt;cntr_type&lt;/code&gt;. Get that column wrong and a perfectly healthy instance can look like it's in crisis, or the reverse.&lt;/p&gt;</description></item></channel></rss>