The WQL Query Builder should highlight, or mark indexed fields to encourage efficient query building.
Many people build inefficient queries simply because they are unaware of the indexed fields available for the views that are referenced by their query. Can the indexed fields be marked?
Cody Mathis
shared this idea
5 comments
-
bdam
commented
Yes please! There's so many poorly written queries out there. Even if you know to use indexed fields ... how can you know which are and which aren't?
Related to this, we should put some kind of preview function that gives results and timing for queries. If we want people to write more efficient queries then let's give them to tools to do so.
-
Dustin Hedges
commented
I would love to see this added into Management Insights if it cannot be done directly within the query editor.
-
Jeff Carreon
commented
This would really help large organizations with large hierarchies for scalability. Most admin console users are NOT aware of indexed vs non-indexed fields. Therefore, performance suffers when many collections are created with non-indexed fields. Please have a way for admins to easily make distinctions between indexed and non-indexed tables.
-
Anonymous
commented
I share this idea
-
Marco Cibis (MS)
commented
I came across many queries in Collections and found that IT-Pros use sometime fileds in their (collection) queries which are not indexed - which has a negative effect on query and collection performance. I would wish that we display the indexed values in bold or colour so you will be aware of the data which gives you better performance. In a second step we may be able to provide an alternative field if available in another attribute class.