sp_BlitzFirst® Result:
Top Queries in the Plan Cache

While sp_BlitzFirst® runs, it takes a sample of SQL Server’s execution plan cache. It identifies queries that used the most resources during that time span – like the most reads, most CPU time, most duration, and most execution count.

You can click on each query to review its execution plan and T-SQL, and then performance tune it to make it go faster (or run less often.)

On slow servers where sp_BlitzFirst® takes too long to run, it bails out and skips the plan cache analysis. If you received the message that plan analysis was skipped, you can either call it with @ExpertMode = 1 to force analysis (which will take a longer time), or try sp_BlitzCache®. That proc lets you define exactly how many plans you want to analyze with its @top parameter, like @top = 10, thereby taking less time for analysis.

For personalized help with getting the right answers for your server, we’ve got SQL Critical Care®.