Performance tuning for number of fields being covered

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Optimization
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      If we have a collection scan generated from a Sargable node, probably should not cover too many fields (e.g. > 5). Also consider avoiding too many fields if there are filters (no need to retrieve a field which we do not need)

            Assignee:
            [DO NOT USE] Backlog - Query Optimization
            Reporter:
            Svilen Mihaylov (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: