Building execution plans is hard: picking the right indexes, seeks vs sorts, row estimations, memory grant requirements, it’s all a lot of work. SQL Server tries to cache execution plans for reuse later, which should result in lower CPU, more memory, and easier troubleshooting. Unfortunately, sometimes it goes wrong. Let’s talk about how it goes...