Change from serverless to provisioned capacity mode in Azure Cosmos DB for NoSQL (preview)
APPLIES TO: NoSQL
Azure Cosmos DB for NoSQL accounts in serverless capacity mode can be changed to provisioned capacity mode. Changing from serverless to provisioned capacity mode converts all containers within the account to manual provisioned throughput containers in-place. The containers' throughput is determined according to the following formula:
Throughput(RU/s) = max(5000, number of partitions * 1000)
.
You can also change the throughput or provisioning mode from manual to autoscale once the migration is complete.
Warning
This is an irreversible operation. Once migrated, the capacity mode can't be changed back to serverless.
Prerequisites
- An existing Azure Cosmos DB for NoSQL account.
- If you have an Azure subscription, create a new account.
- If you don't have an Azure subscription, create a Trial before you begin.
Register for preview
To enable this feature, register for the preview feature Change capacity mode from serverless to provisioned throughput in your subscription.
Change capacity mode
Follow these steps to change the capacity mode using Azure portal.
In the Azure portal, navigate to your API for NoSQL account.
Select the Change capacity mode to provisioned throughput option in the Overview section of the account page.
Review the changes and select Confirm to start the migration.
Monitor the status using the state field in the Overview section. The status indicates that the account is updating while the migration is in progress.
Once the migration is complete, the capacity mode field is now set to provisioned throughput.
Limitations
- This is one time migration that is; the account can't be reversed to serverless capacity mode again.
- There's no SLA associated with the duration of migration.
- Any management operation can't be executed while the migration is in progress.
- In cases where you need to restore a deleted Cosmos DB account, the account is restored to provisioned throughput if the capacity mode was changed from serverless to provisioned, irrespective of the backup timestamp.
- In cases where you need to restore a deleted serverless container within an existing account, which was migrated from serverless to provisioned throughput, contact Microsoft support.