Yearly/Monthly Billing

Application Scenarios

If you want to ensure resource stability over a certain period of time, yearly/monthly billing is a good choice for the following types of workloads:

• Long-term workloads with stable resource requirements, such as official websites, online malls, and blogs.
• Long-term projects, such as scientific research projects and large-scale events.
• Workloads with predictable traffic bursts, for example, e-commerce promotions or festivals.
• Workloads with high data security requirements

Billed Items

You are billed for the following items on a yearly/monthly basis.

If you want to purchase the database audit service of the basic edition for one month, the prices will be displayed as follows:

Billed Usage Period

A yearly/monthly DBSS is billed for the subscription duration. The billing starts when you activated or renewed the subscription (accurate to seconds), and ends at 23:59:59 of the expiry date.

For example, if you purchased a one-month DBSS subscription on March 08, 2023, 15:50:04, the billed usage period is from March 08, 2023, 15:50:04 to April 08, 2023, 23:59:59.

Billing Example

Suppose you purchased a one-month DBSS (basic edition) subscription on June 30, 2023, 15:50:04, and renewed the subscription for one more month before the initial subscription expired. That would include two usage periods:

• Billed usage period 1: June 30, 2023, 15:50:04 to July 30, 2023, 23:59:59.
• Billed usage period 2: July 30, 2023, 23:59:59 to August 30, 2023, 23:59:59.

You will be billed for both usage periods. DBSS resources are billed individually as follows:

The actual calculation is subject to the price in the DBSS Pricing Details.

Price Change After Specification Change

If the specifications of a yearly/monthly DBSS instance no longer meet your needs, you can change the specifications on the console. The system will recalculate the price and either bill or refund you the difference.

• If you upgrade your DBSS specifications, you need to pay the difference in price.
• Currently, you cannot reduce your resource configurations.

Here's an example of upgrading resources without any discounts: Suppose you purchased a one-month database audit instance of the basic edition on July 1, 2023, and upgraded the specifications to the professional edition on July 18, 2023. The price of the original specifications was ¥3,000/month, and that for the new specifications was ¥6,000/month. The price difference will be calculated as follows:

Price difference for the specification upgrade = Price for the new specifications × Remaining period - Price for the original specifications × Remaining period

In this example, Remaining period = 13 (Remaining days in July)/31 (Maximum number of days in July) = 0.419. Cost of upgrade = 6000 x 0.419 – 3000 x 0.419 = ¥1257

Impacts of Expiration

After a DBSS instance is purchased, it enters the valid period and runs normally during this period. If the DBSS instance is not renewed after it expires, before being deleted, it first enters a grace period and then a retention period.

Expiration Reminder

The system will send you a reminder (by email, SMS, or in-app message) 7 days before a yearly/monthly DBSS expires to remind you to renew the subscription.

Impacts of Expiration

If your yearly/monthly DBSS is not renewed after it expires, it changes to the Expired state and enters a grace period. You can use DBSS during the grace period.

If the yearly/monthly DBSS instance is not renewed after the grace period ends, its status turns to Frozen and it enters a retention period. You cannot perform any operations on the resource while it is in the retention period.

If the yearly/monthly DBSS is not renewed by the time the retention period ends, the database audit instance will be released and data cannot be restored.

• For details about renewal, see Overview.