Session State Settings for Cached SQL Server Query Plans
A cached query plan will not be used if the query is different than the original query used to generate the cached plan - makes sense - but what if the query is identical? Well even then the query optimizer may not used the cached query plan. Why? Because all the session settings for the current query request must match those from the first time the query plan was generated and cached. So the question is how can you determine what settings are associated with the cached plan? The answer is in the SQL Server Dynamic Management Objects.
I've spoken quite a bit as of late on the DMOs. These views and functions constructs exist as an abstraction layer for the system tables that are now protected inside of the resource database. The DMOs that accomplish the goal we're looking at examining today are the following:
- sys.dm_exec_cached_plans - Provides a listing of all query plans still residing in cache.
- sys.dm_exec_query_plan - This is a Dynamic Management Function that allows you to pass in a plan_handle (think of it as a unique identifier for a execution plan) as a parameter and return an xml link for the graphical execution plan. When you click on the link, the graphical execution plan opens as a separate tab within Microsoft SQL Server Management Studio. Pretty neat, eh?
- sys.dm_exec_plan_attributes - This is the key DMV for accomplishing the goal we're setting forth. It exposes all session-level settings (attributes as they are referred to in this DMV) for a query plan.
Let's look at the query that puts all of this together:
You may wonder how to determine the plan handle you're interested in querying against. There are many options and in my case I hard-coded the value based upon a specific value I returned from a targeted query against sys.dm_exec_requests for a query that was behaving poorly. The nice thing is that the DMV structure is so extensible. I could easily return results like above for a specific user (for example) by using the following query:
The join structures are quite straight-forward and with the advent of IntelliSense technology in SSMS 2008 (or by use of SQL Prompt for example, which provides the same functionality) the joins usually present themselves. The results in this case are the same, but there is no need for me to do the initial leg work of identifying the exact plan_handle first. You can tailor the query to fit your needs going forth on your own.
Now that you know what session settings are associated with the cached plan, you structure the session state to match the cached plan and take advantage of performance gains that come with plan re-use.
- Read more tips by the author here.
- Interested in Dynamic Management Objects? Here are some more tips at MSSQLTips.com on that subject.
- Query and Performance Tuning tips are accessible via this link.
About the author
View all my tips