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
Copy file name to clipboardExpand all lines: learn-pr/wwl-data-ai/optimize-query-performance-azure-cosmos-db/includes/5-reduce-ru-costs-strategic-indexing.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,10 +6,10 @@ Effective indexing starts with understanding how your application queries data.
6
6
7
7
You can start by cataloging your application's query patterns:
8
8
9
-
1.**Filter properties:** Which properties appear in `WHERE` clauses? Are they equality filters (`=`) or range filters (`>`, `<`)?
10
-
1.**Sort properties:** Which properties appear in `ORDER BY` clauses? What sort directions (ascending or descending) does the application use?
11
-
1.**Property combinations:** Which properties appear together in the same query? Do queries filter on one property and sort by another?
12
-
1.**Access frequency:** How often does each query pattern execute? Prioritize indexes for frequent queries.
9
+
-**Filter properties:** Which properties appear in `WHERE` clauses? Are they equality filters (`=`) or range filters (`>`, `<`)?
10
+
-**Sort properties:** Which properties appear in `ORDER BY` clauses? What sort directions (ascending or descending) does the application use?
11
+
-**Property combinations:** Which properties appear together in the same query? Do queries filter on one property and sort by another?
12
+
-**Access frequency:** How often does each query pattern execute? Prioritize indexes for frequent queries.
13
13
14
14
This analysis reveals which indexes provide the most value. A query that executes thousands of times per minute justifies more index overhead than a query that runs once per day.
0 commit comments