Skip to content

Commit 1fda92e

Browse files
authored
Merge pull request #7613 from srinia/patch-1
Update manage-hyperscale-database.md
2 parents e1b9ba4 + bc817d8 commit 1fda92e

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

azure-sql/database/manage-hyperscale-database.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -166,7 +166,7 @@ In this case, the only backups available would be from steps 5 and 6 of the time
166166

167167
### How to reverse migrate a Hyperscale database to the General Purpose service tier
168168

169-
To reverse migrate an existing Hyperscale database in Azure SQL Database to the Hyperscale service tier, first identify your target service objective in the General Purpose service tier and whether you wish to migrate to the provisioned or serverless compute tiers. Review [resource limits for single databases](resource-limits-vcore-single-databases.md#gen5-compute-generation-part-1) if you aren't sure which service objective is right for your database.
169+
To reverse migrate an existing Hyperscale database in Azure SQL Database to the General Purpose service tier, first identify your target service objective in the General Purpose service tier and whether you wish to migrate to the provisioned or serverless compute tiers. Review [resource limits for single databases](resource-limits-vcore-single-databases.md#gen5-compute-generation-part-1) if you aren't sure which service objective is right for your database.
170170

171171
If you wish to perform an additional service tier change after reverse migrating to General Purpose, identify your eventual target service objective as well and ensure that your database's allocated size is small enough to fit in that service objective.
172172

0 commit comments

Comments
 (0)