Skip to content

Commit 86c24b7

Browse files
Refine indexing strategies for query performance
Updated the section on effective indexing strategies by refining the list of considerations for indexing based on query patterns.
1 parent bb3213c commit 86c24b7

1 file changed

Lines changed: 4 additions & 4 deletions

File tree

learn-pr/wwl-data-ai/optimize-query-performance-azure-cosmos-db/includes/5-reduce-ru-costs-strategic-indexing.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,10 +6,10 @@ Effective indexing starts with understanding how your application queries data.
66

77
You can start by cataloging your application's query patterns:
88

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.
1313

1414
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.
1515

0 commit comments

Comments
 (0)