Most likely you like the caching effect. When you first run the query, SQL generates a execution plan and then caches it. If you run the query again, it will remember the execution plan, and in some cases you will see an increase in speed. Therefore, if you are testing a request, you need to clear the cache. That's what I'm doing.
Quote from Devx website ( DEVx tooltip )
run DBCC DROPCLEANBUFFERS, which clears all data from the cache. Then run DBCC FREEPROCCACHE, which will clear the stored procedure cache.
NTN
source share