Log when and why a query shape begins to use a different plan

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Diagnostics, Querying
    • None
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • 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.

            Assignee:
            Unassigned
            Reporter:
            Charlie Page (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: