How can I create a database with provisioned throughput?
See original GitHub issueI don’t see a way to create a database with shared throughput in the new SDK.
public virtual Task<DatabaseResponse> CreateDatabaseIfNotExistsAsync(string id, int? throughput = null, RequestOptions requestOptions = null, CancellationToken cancellationToken = default);
RequestOptions
doesn’t have a property for this purpose. Is it currently possible to create a new database with shared throughput?
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Introduction to provisioned throughput in Azure Cosmos DB
Learn how to set provisioned throughput for your Azure Cosmos DB containers and databases.
Read more >Managing settings on DynamoDB provisioned capacity ...
When you create a new provisioned table in Amazon DynamoDB, you must specify its provisioned throughput capacity. This is the amount of read...
Read more >How to reconfigure a Cosmos database to have shared ...
1 Answer 1 ... You have to create a new database. Changing the existing database is not supported: A container with provisioned throughput...
Read more >Autoscale provisioned throughput for Azure Cosmos DB ...
Deborah joins Mark to talk about autoscale provisioned throughput in Azure Cosmos DB. Autoscale eliminates manual throughput management and ...
Read more >Choose when to use database-level provisioned throughput
And here, let's take a look at the two ways that we provision Request Units, database level, and container level. Here on this...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
On the portal, if I create a new database without checking the above checkbox, then I get something like this:
If I check the checkbox, I get this:
When I executed
CreateDatabaseIfNotExistsAsync
with an explicit throughput, I ended up creating a database that looked like the first one. Every subsequent container then defaulted to 400 throughput because the database did not set a throughput of its own.Let me verify this one more time tonight.
Tested this again and it seems to be working. I’m not sure what was happening last night. I think the issue might have been as described in @simplynaveen20’s post.