如何在 Azure SQL 数据库中从 DTU 迁移到 vCore

How to move from DTU to vCore in Azure SQL Database

目前我们的 Azure 资源有 3 个(开发、QA 和生产)阶段。这三个都在使用 SQL 数据库 'Standard S6: 400 DTUs'。由于 Dev 和 QA SQL 数据库,我们每月的成本超过 700 欧元。我计划从 DTU 迁移到 vCore 无服务器。以下是我的查询,

  1. 只是进入门户 -> 计算和存储 -> 然后从 DTU 更改为 vCore Serverless 是正确的过程吗?
  2. 做这个手术之前还需要带其他东西吗?
  3. 我现有的 Azure SQL 数据库是否会受到此操作的影响?
  4. 如果情况不符合我的要求,我可以用同样的方法返回 DTU 模式。

提前致谢。

您可以查看此 MS 文档了解详细信息:Migrate Azure SQL Database from the DTU-based model to the vCore-based model

  1. 刚刚进入门户 -> 计算和存储 -> 并从 DTU 到 vCore Serverless 是正确的过程吗?

Yes! just change to required option from dropdown and click on Apply. Migrating a database from the DTU-based purchasing model to the vCore-based purchasing model is similar to scaling between service objectives in the Basic, Standard, and Premium service tiers, with similar duration and a minimal downtime at the end of the migration process.

  1. 做这个手术之前还需要带其他东西吗?
  • Some hardware generations may not be available in every region. Check availability under Hardware generations for SQL Database.
  • In the vCore model, the supported maximum database size may differ depending on hardware generation. For large databases, check supported maximum sizes in the vCore model for single databases and elastic pools.
  • If you have geo-replicated databases, during migration, you don't have to stop geo-replication, but you must upgrade the secondary database first, and then upgrade the primary. When downgrading, reverse the order Also go through the doc once.
  1. 我现有的 Azure SQL 数据库是否会受此影响 操作?

You can copy any database with a DTU-based compute size to a database with a vCore-based compute size without restrictions or special sequencing as long as the target compute size supports the maximum database size of the source database. Database copy creates a transactionally consistent snapshot of the data as of a point in time after the copy operation starts. It doesn't synchronize data between the source and the target after that point in time.

  1. 如果事情不符合我的要求,我可以来吗 回到 DTU 模式。

A database migrated to the vCore-based purchasing model can be migrated back to the DTU-based purchasing model at any time in the same fashion, with the exception of databases migrated to the Hyperscale service tier.