windows azure mysql data disk_为计算预付预留容量-Azure Database for MySQL | Microsoft Docs

本文主要是介绍windows azure mysql data disk_为计算预付预留容量-Azure Database for MySQL | Microsoft Docs,希望对大家解决编程问题提供一定的参考价值,需要的开发者们随着小编来一起学习吧!

您现在访问的是微软AZURE全球版技术文档网站,若需要访问由世纪互联运营的MICROSOFT AZURE中国区技术文档网站,请访问 https://docs.azure.cn.

为 Azure Database for MySQL 计算资源预付预留容量Prepay for Azure Database for MySQL compute resources with reserved capacity

05/20/2020

本文内容

与即用即付价格相比,Azure Database for MySQL 现在可为计算资源事先预付节省资金。Azure Database for MySQL now helps you save money by prepaying for compute resources compared to pay-as-you-go prices. 利用 Azure Database for MySQL 预留容量,你可以在一年或三年期限内提前提交 MySQL 服务器,以获得有关计算成本的重要折扣。With Azure Database for MySQL reserved capacity, you make an upfront commitment on MySQL server for a one or three year period to get a significant discount on the compute costs. 若要购买 Azure Database for MySQL 保留容量,需要指定 Azure 区域、部署类型、性能层和术语。To purchase Azure Database for MySQL reserved capacity, you need to specify the Azure region, deployment type, performance tier, and term.

不需要将保留分配给特定 Azure Database for MySQL 服务器。You do not need to assign the reservation to specific Azure Database for MySQL servers. 已在运行的 Azure Database for MySQL 或新部署的,将自动获得预留价格的好处。An already running Azure Database for MySQL or ones that are newly deployed, will automatically get the benefit of reserved pricing. 购买预留容量便会预付为期一年或三年的计算资源费用。By purchasing a reservation, you are pre-paying for the compute costs for a period of one or three years. 购买保留后,与预订属性匹配的 Azure database for MySQL 计算费用将不再按即用即付费率收费。As soon as you buy a reservation, the Azure database for MySQL compute charges that match the reservation attributes are no longer charged at the pay-as-you go rates. 预订不涉及与 MySQL 数据库服务器相关联的软件、网络或存储费用。A reservation does not cover software, networking, or storage charges associated with the MySQL Database server. 在保留期结束时,计费权益过期,按即用即付价格对 Azure Database for MySQL 进行计费。At the end of the reservation term, the billing benefit expires, and the Azure Database for MySQL are billed at the pay-as-you go price. 虚拟机预留实例不自动续订。Reservations do not auto-renew.

可以在 Azure 门户中购买 Azure Database for MySQL 保留容量。You can buy Azure Database for MySQL reserved capacity in the Azure portal. 通过提前付款或按月付款的方式为预留付款。购买保留容量:To buy the reserved capacity:

对于至少一个企业或个人订阅,你必须以即用即付费率作为所有者角色。You must be in the owner role for at least one Enterprise or individual subscription with pay-as-you-go rates.

对于企业订阅,必须在 EA 门户中启用“添加预留实例”。For Enterprise subscriptions, Add Reserved Instances must be enabled in the EA portal. 或者,如果禁用了该设置,则必须是订阅的 EA 管理员。Or, if that setting is disabled, you must be an EA Admin on the subscription.

对于云解决方案提供商 (CSP) 计划中,只有管理员代理或销售代理才能购买 Azure Database for MySQL 保留容量。For Cloud Solution Provider (CSP) program, only the admin agents or sales agents can purchase Azure Database for MySQL reserved capacity.

在购买之前确定正确的数据库大小Determine the right database size before purchase

保留的大小应基于特定区域中现有或即将部署的服务器使用的计算总量,并使用相同的性能层和硬件生成。The size of reservation should be based on the total amount of compute used by the existing or soon-to-be-deployed server within a specific region and using the same performance tier and hardware generation.

例如,假设你正在运行一个通用的 Gen5 – 32 vCore MySQL 数据库,以及两个内存优化的 Gen5-16 vCore MySQL 数据库。For example, let's suppose that you are running one general purpose, Gen5 – 32 vCore MySQL database, and two memory optimized, Gen5 – 16 vCore MySQL databases. 接下来,假设你计划在下个月中部署一个额外的常规用途: Gen5 – 32 vCore 数据库服务器和一个内存优化的 Gen5 – 16 vCore 数据库服务器。Further, let's supposed that you plan to deploy within the next month an additional general purpose, Gen5 – 32 vCore database server, and one memory optimized, Gen5 – 16 vCore database server. 假设你知道,你将需要至少1年的这些资源。Let's suppose that you know that you will need these resources for at least 1 year. 在这种情况下,你应该购买 64 (2x32) Vcore,1年保留用于单个数据库常规用途-Gen5 和 48 (2x16 + 16) vCore 1 年保留用于单个数据库内存优化-Gen5In this case, you should purchase a 64 (2x32) vCores, 1 year reservation for single database general purpose - Gen5 and a 48 (2x16 + 16) vCore 1 year reservation for single database memory optimized - Gen5

购买 Azure Database for MySQL 保留的容量Buy Azure Database for MySQL reserved capacity

选择“所有服务” > “预订”。Select All services > Reservations.

选择 " 添加 ",然后在 "购买预订" 窗格中选择 " Azure Database for MySQL ",为 MySQL 数据库购买新的保留。Select Add and then in the Purchase reservations pane, select Azure Database for MySQL to purchase a new reservation for your MySQL databases.

填写必填字段。Fill-in the required fields. 与所选属性匹配的现有或新数据库可以获取预留容量折扣。Existing or new databases that match the attributes you select qualify to get the reserved capacity discount. 获取折扣的 Azure Database for MySQL 服务器的实际数目取决于所选的范围和数量。The actual number of your Azure Database for MySQL servers that get the discount depend on the scope and quantity selected.

9df5231ffbd71d356c0eb0c6b0b19cc4.png

下表描述了必填字段。The following table describes required fields.

字段Field

说明Description

订阅Subscription

用于支付 Azure Database for MySQL 预留容量预留的订阅。The subscription used to pay for the Azure Database for MySQL reserved capacity reservation. 订阅上的付款方式将收取 Azure Database for MySQL 预留容量预留的前期成本。The payment method on the subscription is charged the upfront costs for the Azure Database for MySQL reserved capacity reservation. 订阅类型必须是企业协议 (产品/服务编号: BC-OP-NT-AZR-Ms-azr-0017p 或 BC-OP-NT-AZR-Ms-azr-0148p) 或使用即用即付定价 (产品/服务的个人协议产品/服务) 。The subscription type must be an enterprise agreement (offer numbers: MS-AZR-0017P or MS-AZR-0148P) or an individual agreement with pay-as-you-go pricing (offer numbers: MS-AZR-0003P or MS-AZR-0023P). 对于企业订阅,将从注册的 Azure 预付款 (之前称为货币承诺) 余额或按超额支付收费。For an enterprise subscription, the charges are deducted from the enrollment's Azure Prepayment (previously called monetary commitment) balance or charged as overage. 对于使用即用即付定价的单个订阅,将对订阅上的信用卡或发票付款方式收取费用。For an individual subscription with pay-as-you-go pricing, the charges are billed to the credit card or invoice payment method on the subscription.

范围Scope

VCore 预订的范围可以包含一个订阅或多个订阅 (共享范围) 。The vCore reservation's scope can cover one subscription or multiple subscriptions (shared scope). 如果选择:If you select: 共享,vCore 预订折扣应用于计费上下文内任何订阅中运行的 Azure Database for MySQL 服务器。Shared, the vCore reservation discount is applied to Azure Database for MySQL servers running in any subscriptions within your billing context. 对于企业客户,共享范围是注册范围,包括注册中的所有订阅。For enterprise customers, the shared scope is the enrollment and includes all subscriptions within the enrollment. 对于即用即付客户,共享范围是由帐户管理员创建的所有即用即付订阅。For Pay-As-You-Go customers, the shared scope is all Pay-As-You-Go subscriptions created by the account administrator. 单个订阅,vCore 预订折扣将应用到此订阅中的 Azure Database for MySQL 服务器。Single subscription, the vCore reservation discount is applied to Azure Database for MySQL servers in this subscription. 单个资源组,预订折扣应用于所选订阅中的 Azure Database for MySQL 服务器,以及该订阅内的所选资源组。Single resource group, the reservation discount is applied to Azure Database for MySQL servers in the selected subscription and the selected resource group within that subscription.

区域Region

Azure Database for MySQL 保留容量保留所涵盖的 Azure 区域。The Azure region that's covered by the Azure Database for MySQL reserved capacity reservation.

部署类型Deployment Type

要为其购买预订的 Azure Database for MySQL 资源类型。The Azure Database for MySQL resource type that you want to buy the reservation for.

性能层Performance Tier

Azure Database for MySQL 服务器的服务层。The service tier for the Azure Database for MySQL servers.

术语Term

一年One year

数量Quantity

在 Azure Database for MySQL 保留容量保留内购买的计算资源量。The amount of compute resources being purchased within the Azure Database for MySQL reserved capacity reservation. 该数量是所选 Azure 区域和正在保留的性能层中的 Vcore 数,将获得计费折扣。The quantity is a number of vCores in the selected Azure region and Performance tier that are being reserved and will get the billing discount. 例如,如果你正在运行或计划运行具有 Gen5 16 Vcore 的总计算能力的 Azure Database for MySQL 服务器,则会将数量指定为16,以最大程度地提高所有服务器的权益。For example, if you are running or planning to run an Azure Database for MySQL servers with the total compute capacity of Gen5 16 vCores in the East US region, then you would specify quantity as 16 to maximize the benefit for all servers.

对预留执行取消、交换或退款操作Cancel, exchange, or refund reservations

可以在一定的限制下对预留执行取消、交换或退款操作。You can cancel, exchange, or refund reservations with certain limitations.

vCore 大小灵活性vCore size flexibility

vCore 大小灵活性有助于在同一性能层和区域内纵向扩展或收缩,且不会丢失预留容量权益。vCore size flexibility helps you scale up or down within a performance tier and region, without losing the reserved capacity benefit.

需要帮助?Need help ? 联系我们Contact us

如有任何疑问或需要帮助,请创建支持请求。If you have questions or need help, create a support request.

后续步骤Next steps

VCore 预订折扣将自动应用于与 Azure Database for MySQL 保留容量预留范围和属性匹配的 Azure Database for MySQL 服务器数。The vCore reservation discount is applied automatically to the number of Azure Database for MySQL servers that match the Azure Database for MySQL reserved capacity reservation scope and attributes. 可以通过 Azure 门户、PowerShell、CLI 或通过 API 来更新 Azure database for MySQL 保留容量保留的范围。You can update the scope of the Azure database for MySQL reserved capacity reservation through Azure portal, PowerShell, CLI or through the API.

若要了解如何管理 Azure Database for MySQL 预留容量,请参阅管理 Azure Database for MySQL 保留容量。To learn how to manage the Azure Database for MySQL reserved capacity, see manage Azure Database for MySQL reserved capacity.

若要了解有关 Azure 预订的详细信息,请参阅以下文章:To learn more about Azure Reservations, see the following articles:

这篇关于windows azure mysql data disk_为计算预付预留容量-Azure Database for MySQL | Microsoft Docs的文章就介绍到这儿,希望我们推荐的文章对编程师们有所帮助!



http://www.chinasem.cn/article/311014

相关文章

SQL中的外键约束

外键约束用于表示两张表中的指标连接关系。外键约束的作用主要有以下三点: 1.确保子表中的某个字段(外键)只能引用父表中的有效记录2.主表中的列被删除时,子表中的关联列也会被删除3.主表中的列更新时,子表中的关联元素也会被更新 子表中的元素指向主表 以下是一个外键约束的实例展示

基于MySQL Binlog的Elasticsearch数据同步实践

一、为什么要做 随着马蜂窝的逐渐发展,我们的业务数据越来越多,单纯使用 MySQL 已经不能满足我们的数据查询需求,例如对于商品、订单等数据的多维度检索。 使用 Elasticsearch 存储业务数据可以很好的解决我们业务中的搜索需求。而数据进行异构存储后,随之而来的就是数据同步的问题。 二、现有方法及问题 对于数据同步,我们目前的解决方案是建立数据中间表。把需要检索的业务数据,统一放到一张M

如何去写一手好SQL

MySQL性能 最大数据量 抛开数据量和并发数,谈性能都是耍流氓。MySQL没有限制单表最大记录数,它取决于操作系统对文件大小的限制。 《阿里巴巴Java开发手册》提出单表行数超过500万行或者单表容量超过2GB,才推荐分库分表。性能由综合因素决定,抛开业务复杂度,影响程度依次是硬件配置、MySQL配置、数据表设计、索引优化。500万这个值仅供参考,并非铁律。 博主曾经操作过超过4亿行数据

性能分析之MySQL索引实战案例

文章目录 一、前言二、准备三、MySQL索引优化四、MySQL 索引知识回顾五、总结 一、前言 在上一讲性能工具之 JProfiler 简单登录案例分析实战中已经发现SQL没有建立索引问题,本文将一起从代码层去分析为什么没有建立索引? 开源ERP项目地址:https://gitee.com/jishenghua/JSH_ERP 二、准备 打开IDEA找到登录请求资源路径位置

MySQL数据库宕机,启动不起来,教你一招搞定!

作者介绍:老苏,10余年DBA工作运维经验,擅长Oracle、MySQL、PG、Mongodb数据库运维(如安装迁移,性能优化、故障应急处理等)公众号:老苏畅谈运维欢迎关注本人公众号,更多精彩与您分享。 MySQL数据库宕机,数据页损坏问题,启动不起来,该如何排查和解决,本文将为你说明具体的排查过程。 查看MySQL error日志 查看 MySQL error日志,排查哪个表(表空间

MySQL高性能优化规范

前言:      笔者最近上班途中突然想丰富下自己的数据库优化技能。于是在查阅了多篇文章后,总结出了这篇! 数据库命令规范 所有数据库对象名称必须使用小写字母并用下划线分割 所有数据库对象名称禁止使用mysql保留关键字(如果表名中包含关键字查询时,需要将其用单引号括起来) 数据库对象的命名要能做到见名识意,并且最后不要超过32个字符 临时库表必须以tmp_为前缀并以日期为后缀,备份

poj 1113 凸包+简单几何计算

题意: 给N个平面上的点,现在要在离点外L米处建城墙,使得城墙把所有点都包含进去且城墙的长度最短。 解析: 韬哥出的某次训练赛上A出的第一道计算几何,算是大水题吧。 用convexhull算法把凸包求出来,然后加加减减就A了。 计算见下图: 好久没玩画图了啊好开心。 代码: #include <iostream>#include <cstdio>#inclu

uva 1342 欧拉定理(计算几何模板)

题意: 给几个点,把这几个点用直线连起来,求这些直线把平面分成了几个。 解析: 欧拉定理: 顶点数 + 面数 - 边数= 2。 代码: #include <iostream>#include <cstdio>#include <cstdlib>#include <algorithm>#include <cstring>#include <cmath>#inc

uva 11178 计算集合模板题

题意: 求三角形行三个角三等分点射线交出的内三角形坐标。 代码: #include <iostream>#include <cstdio>#include <cstdlib>#include <algorithm>#include <cstring>#include <cmath>#include <stack>#include <vector>#include <

[MySQL表的增删改查-进阶]

🌈个人主页:努力学编程’ ⛅个人推荐: c语言从初阶到进阶 JavaEE详解 数据结构 ⚡学好数据结构,刷题刻不容缓:点击一起刷题 🌙心灵鸡汤:总有人要赢,为什么不能是我呢 💻💻💻数据库约束 🔭🔭🔭约束类型 not null: 指示某列不能存储 NULL 值unique: 保证某列的每行必须有唯一的值default: 规定没有给列赋值时的默认值.primary key: