This is the second of two connected posts on SQL Server memory. In this post, Kevin Kline focuses on the moving parts that turn into real incidents: plan cache bloat, inefficient query patterns, practical troubleshooting, and how observability tools shorten the path from symptom to root cause.
In Part 1, we looked at how SQL Server uses memory, why “SQL Server takes care of that” stops being enough, and which configuration habits make life easier.