Hi, I am from Azure Cosmos DB Engineering Team. @llcoolv has responded and the response is correct. For scenarios where you create a lot of collections/tables

Hi, I am from Azure Cosmos DB Engineering Team. @llcoolv has responded and the response is correct. For scenarios where you create a lot of collections/tables, we recommend to provision throughput on a database and share the provisioned throughput among all the containers – to save on costs. You can change the throughput at database exactly like how you will change the throughput at container level. It is the same API, it is supported via CLI, SDK, Rest API and Portal as well. The entry point for database level throughout is 400RUs $24 per month and you can add any number of collections/tables that can share this throughput. You can scale up and down in the increments of 100RUs (or $6/month). Please see the following links for details: [1] https://docs.microsoft.com/en-us/azure/cosmos-db/set-throughput https://docs.microsoft.com/en-us/azure/cosmos-db/set-through... [2] https://docs.microsoft.com/en-us/azure/cosmos-db/how-to-provision-container-throughput https://docs.microsoft.com/en-us/azure/cosmos-db/how-to-prov... [3] https://docs.microsoft.com/en-us/azure/cosmos-db/how-to-provision-database-throughput https://docs.microsoft.com/en-us/azure/cosmos-db/how-to-prov... Please see the sample here for moving data: [4] https://github.com/Azure/azure-documentdb-dotnet/tree/master/samples/ChangeFeedMigrationTool https://github.com/Azure/azure-documentdb-dotnet/tree/master... Thanks!