I am trying to review if there is a way to track throughput changes for Azure Cosmos DB when using manual throughput. Please if you can provide any pointers.
Related
Doesn't Azure support Geo-Redundancy and Multi-region Writes options for serverless CosmosDB Core(SQL) account? But, those options are listed for Provisioned throughput capacity.
Yes you are right, It's a limitation with Serverless Accounts, According to docs,
A serverless account can only run in a single Azure region. It is not
possible to add additional Azure regions to a serverless account after
you create it.
There is some work being done in this area, but there is no ETA yet.
I tested setup Azure Purview and CosmosDB with Provisioned throughput capacity/ serverless capacity mode SQL API with few collections. After Cosmos Data source registration, I initiated scan and provided key vault with secret pointing to CosmosDB account key.
For CosmosDB with Provisioned throughput capacity mode, data assets were discovered successfully.
For capacity mode - serverless CosmosDB SQL API, collection items were not identified as data assets after scan completion.
For CosmosDB with Provisioned throughput capacity mode, data assets were discovered successfully.
For capacity mode - serverless CosmosDB SQL API, collection items were not identified as data assets after scan completion.
Does cosmosdb cassandra api uses same memtable , commit log, systable compaction write path to provide good performance for heavy write operations or is it same as the write operations in cosmos sql api.
Will cosmos cassndra api is suppose to work better then write same no. of write operations in cosmos sql api?
Currently in Application Insights we are only seeing these operations between our .Net Core application and Cosmos db
but queries to actually query and insert data is not seen. We are using Direct connection mode as per the performance tips https://learn.microsoft.com/en-us/azure/cosmos-db/performance-tips.
Do we have to manually track these queries or can this be done automatically, like when using Sql Server.
I turns out that queries to cosmos db using Direct connection mode are not automatically tracked, as stated here: https://learn.microsoft.com/en-us/azure/azure-monitor/app/asp-net-dependencies#automatically-tracked-dependencies
So all queries to Cosmos db must be tracked manually.
I am using Azure Cosmos DB as my database. Just wondering how many database instance I can create under my Azure account? It is saying that the starting instance number is 200 per account. I may need around 1000 database instance per my tenant.
Thanks advanced.
Here is a feeback about the limitation of total databases number per Cosmos DB account. Also, I checked this issue on my side, and this limitation for 100 databases per Cosmos DB account still remains. For Azure Cosmos DB account number limit per subscription, I checked DocumentDB limits, but find nothing useful information. I have 20+ Cosmos DB account under my subscription. I assumed that you could send email to askdocdb#microsoft.com for more details about limitation of Azure Cosmos DB.
Currently the Azure Cosmos DB service quotas documentation states that you can have unlimited number of databases per account, so if there has been any limitations before they seem to be lifted. Just beware, it can get costly.