You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
SQL Server is picking some wack query plans when hitting the plan cache looking for SQL Handles related to deadlocked queries
Describe the solution you'd like
Drop qualifying rows into an intermediate temp table from sys.dm_exec_query_stats and then get query plans only with those rows.
Describe alternatives you've considered
Updating the #available_plans temp table to make it look like it has a ton of rows in it so the optimizer chooses and eager index spool plan. But that doesn't port to RDS, like we discovered with the #t temp table uses to encourage a parallel plan when reading the XML data.
Are you ready to build the code for the feature?
Yes I made it already when working through the same issue with sp_HumanEventsBlockViewer.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
SQL Server is picking some wack query plans when hitting the plan cache looking for SQL Handles related to deadlocked queries
Describe the solution you'd like
Drop qualifying rows into an intermediate temp table from
sys.dm_exec_query_stats
and then get query plans only with those rows.Describe alternatives you've considered
Updating the #available_plans temp table to make it look like it has a ton of rows in it so the optimizer chooses and eager index spool plan. But that doesn't port to RDS, like we discovered with the #t temp table uses to encourage a parallel plan when reading the XML data.
Are you ready to build the code for the feature?
Yes I made it already when working through the same issue with sp_HumanEventsBlockViewer.
The text was updated successfully, but these errors were encountered: