Optimize query performance with Azure Cosmos DB indexing metrics | Azure Friday

Learn how to use the new Azure Cosmos DB indexing metrics to improve query performance. Tim Sander shows Scott Hanselman how to obtain, interpret, and make changes based on the indexing metrics.
00:00 - Introduction
02:23 - Default indexing policy
04:18 - Optimizing for write performance
07:23 - Index metrics
09:32 - Composite indexes
16:42 - Roadmap insights
18:00 - Wrap-up
🔗 Optimize query performance with Azure Cosmos DB indexing metrics - aka.ms/azfr/714/01
🔗 Troubleshoot query issues when using Azure Cosmos DB - aka.ms/azfr/714/02
🔗 New ways to use composite indexes in Azure Cosmos DB - aka.ms/azfr/714/03
🔗 Indexing metrics in Azure Cosmos DB - aka.ms/azfr/714/04
🔗 Create a free account (Azure) - aka.ms/azfr/714/free
🔗 Create a Pay as You Go account (Azure) - aka.ms/azfr/714/payg
#Microsoft #Azure #AzureFriday

[@ndamulelosbg8887]

Great Info, Thanks team👍

[@makeyourlifewith.]

is it same cosmos MongoDB?

[@mystiqkc]

Why is indexing all properties expensive? Giving a little info on this would give users an idea of why thinking of indexes is important

[@evezero9834]

As he said... It is only expensive for writing operations (because all affected indexes have to be changed).

[@mystiqkc]

2 RUs being cheap is relative, for example if you make thousands of queries per day, 2 RUs might not be cheap. Wish the presenter talked about this

[@GurpreetSingh-wx5yi]

RUs are Request units per second. So, a thousand queries is still pretty cheap if it is per day