Hi @Naren
PLE = (SQL Max memory(GB)/4)*300
This calculation is right. If your PLE goes down suddenly, then the first thing should be to check memory allocation. Is it enough amount of size for the SQL Server? If yes, then check the currently executing request, is there any long-running thread that consumes more memory? If yes, then review the currently executing query statement.
Unnecessary memory usage issue should be observed and take a chance to get it optimized with a proper investigation.
- Which objects are using the more buffer cache memory?
- Allotment of object indexes and partitions are accurate and effective.
Users can monitor it with querying on sys.dm_os_performance_counters DMV to find that PLE threshold is crossing the underline or not. If the counter value found is less than your calculation, then it should trigger a mail to the responsible team to observe and monitor the memory pressure-related parameters.
Please refer to this article for more details: Page Life Expectancy (PLE) in SQL Server.
Best regards,
Cosmog Hong
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our Documentation to enable e-mail notifications if you want to receive the related email notification for this thread.