Azure Cosmos DB Query Engine Performance Improvements - Episode 52

Подписаться 9 тыс.

50% 1

In this episode, Justine Cocchi returns to discuss with Mark Brown the recent improvements in the Azure Cosmos DB query engine. Learn about a new system function and optimizations for a set of query operations to better use the index in the Azure Cosmos DB Core (SQL) API. We’ll cover the new DateTimeBin function as well as improvements to GROUP BY, DISTINCT, OFFSET LIMIT, and JOIN.
Learn more:
* Introducing a new system function and optimized query operators - aka.ms/cosmosd...
* GROUP BY clause in Azure Cosmos DB | Microsoft Docs - aka.ms/cosmosd...
* SQL keywords for Azure Cosmos DB | Microsoft Docs - aka.ms/cosmosd...
* OFFSET LIMIT clause in Azure Cosmos DB | Microsoft Docs - aka.ms/cosmosd...
* SQL JOIN queries for Azure Cosmos DB | Microsoft Docs - aka.ms/cosmosd...
* Optimizing for development and testing in Azure Cosmos DB | Microsoft Docs - aka.ms/cosmosd...
* Try Azure Cosmos DB - aka.ms/trycosm...
#azurecosmosdb #azure #nosql #cloud

Опубликовано:

22 сен 2024

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 4

@pk4866 2 года назад

Team, excellent presentation. Please upload the datasets and console app code to test.

@martinsmith8670 4 месяца назад

I'm surprised by the order of the composite index shown at 15:09 for the query "SELECT AVG(c.Price), c.Category FROM c GROUP BY c.Category" - for a relational database the best composite index would be (Category, Price) - as then the query engine can just scan the index in order and use the fact that the index is ordered by Category to do the grouping. (whenever it sees a new Category value from previous or runs out of rows it can emit the aggregated value for the previous group) - but this composite index shown seems to be ordered by Price first?