Performance Myths: The query result cache
I was recently doing a training session when a developer commented that it was OK to run an expensive query twice because on the second execution, SQL Server would use the “results cache” and be “practically free”. It’s not the first time I’ve heard someone refer to a “results cache” in SQL Server. If you don’t know better, you might think SQL Server has a “results cache” because the second execution of a query is often faster.