-
Type: Improvement
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Diagnostics, Querying
-
None
Currently, if a plan occasionally flips flops to a less optimal query (or a bug occurs) it can be extremely challenging (or impossible), to catch the plan cache in the bad state.
Setting the QLOG on for all queries isn't reasonable as that generates too much output for high use systems.
Having an option to only output the QLOG if the plan changes so that the reason for change can be recorded automatically enable the quick diagnosis of these cases.
- duplicates
-
SERVER-13220 Add and expose statistics to new query framework
- Backlog
- is related to
-
SERVER-18013 Expose more execution stats from plan cache introspection commands
- Closed
-
SERVER-18468 Include query planning details on query log lines
- Closed