All Products
Search
Document Center

Database Autonomy Service:Billing overview

Last Updated:Aug 30, 2024

This topic describes the billing of different editions of Database Autonomy Service (DAS), including the billing methods and billable items. This topic also describes the supported databases and regions of different DAS editions.

Billing of DAS editions

DAS provides three editions: Basic Edition, Cost-efficient Edition, and Enterprise Edition. The Enterprise Edition is formerly known as Professional Edition.

  • DAS Basic Edition: By default, this edition is activated and free of charge. DAS Basic Edition supports centralized management of multiple database engines and provides the database diagnostics and performance optimization features. This edition helps you in daily database O&M and management.

  • DAS Cost-efficient Edition: You are charged for using this edition based on the subscription billing method. Based on the features of DAS Basic Edition, this edition supports lightweight autonomy services, provides the automatic tablespace fragment recycling and performance insight features, and updates features such as session management and lock analysis.

  • DAS Enterprise Edition (formerly known as Professional Edition): You are charged for using this edition. Based on the features of DAS Cost-efficient Edition, this edition provides the SQL Explorer and Audit feature.

    Important

    With ongoing updates and evolution, DAS Enterprise Edition now has multiple versions available. When you activate DAS Enterprise Edition for a database instance, you can activate only the latest version of DAS Enterprise Edition that is supported by the database instance. As DAS Enterprise Edition continues to update, its billing becomes more flexible, and the usage cost decreases accordingly.

Billing methods and billable items

The following table describes the billing methods and billable items of different DAS editions.

Note

On the Edition Management page in the DAS console, you can view the DAS editions that are activated for database instances.

Edition

Version

Billing method

Billable item

DAS Basic Edition

N/A

Free of charge

N/A

DAS Cost-efficient Edition

N/A

Subscription

  • Basic plan

  • Medium plan

  • Advanced plan

DAS Enterprise Edition

V3

Pay-as-you-go

Important

If DAS Enterprise Edition V3 is activated for a database instance, you are charged for log traffic and cold data storage by default. You are also charged for other features based on your actual usage.

  • Default fees:

    • Log traffic

    • Cold data storage

  • Fees billed by usage:

    • Log indexing

    • SQL Explorer

    • Hot data storage

    • Cold data query

    • Download (free of charge)

V2 (formerly known as DAS Professional Edition of the new version)

Pay-as-you-go

  • Hot data storage

  • Cold data storage

  • Data query

V1 (formerly known as DAS Professional Edition of the previous version)

Subscription and pay-as-you-go

  • Quota of DAS Enterprise Edition V1 (subscription)

    Note

    The quota indicates the number of database instances for which DAS Enterprise Edition V1 can be activated.

  • Storage for SQL Explorer data (pay-as-you-go)

V0 (formerly known as DAS Professional Edition of the previous version that uses the previous link)

Pay-as-you-go

  • Storage for SQL Explorer data

  • For more information about the billing of each edition, see Billing details.

  • For more information about the features that are supported by each edition, see DAS editions and supported features.

  • You can migrate data from DAS Enterprise Edition V1 or DAS Enterprise Edition V2 to DAS Enterprise Edition V3 free of charge. Before the migration is complete, you are charged based on the source version. After the migration is complete, you are charged based on the destination version. For more information, see the "How do I migrate data between different versions of DAS Enterprise Edition?" section of the FAQ topic.

Important

If you want to activate DAS Enterprise Edition for your database instance, do not activate multiple versions of DAS Enterprise Edition for the database instance on the Edition Management page. Otherwise, you are charged for the earliest version of DAS Enterprise Edition. If you have activated multiple versions of DAS Enterprise Edition for your database instance, you can deactivate the versions that you no longer need on the Edition Management page. Then, you are charged for the version that is in use. For more information, see Disable DAS Cost-efficient Edition and DAS Enterprise Edition.

Supported databases and regions

DAS Enterprise Edition V3

Database instance

Region

  • ApsaraDB RDS for MySQL

  • PolarDB for MySQL

China (Hangzhou), China (Shanghai), China (Qingdao), China (Beijing), China (Zhangjiakou), China (Hohhot), China (Ulanqab), China (Shenzhen), China (Heyuan), China (Guangzhou), China (Chengdu), China (Hong Kong), Singapore, Japan (Tokyo), Malaysia (Kuala Lumpur), Indonesia (Jakarta), UK (London), US (Silicon Valley), US (Virginia), and Germany (Frankfurt)

ApsaraDB RDS for PostgreSQL

China (Qingdao), China (Beijing), China (Zhangjiakou), China (Hohhot), China (Ulanqab), China (Hangzhou), China (Shanghai), China (Shenzhen), China (Heyuan), China (Guangzhou), China (Chengdu), China (Hong Kong), Singapore, Indonesia (Jakarta), Japan (Tokyo), US (Virginia), Germany (Frankfurt), and UK (London)

ApsaraDB RDS for SQL Server

China (Qingdao), China (Beijing), China (Zhangjiakou), China (Hohhot), China (Ulanqab), China (Hangzhou), China (Shanghai), China (Shenzhen), China (Heyuan), China (Guangzhou), China (Chengdu), China (Hong Kong), Singapore, Malaysia (Kuala Lumpur), Japan (Tokyo), Indonesia (Jakarta), US (Silicon Valley), US (Virginia), and Germany (Frankfurt)

DAS Enterprise Edition V2

Database instance

Region

  • ApsaraDB RDS for MySQL

  • PolarDB for MySQL

China (Hangzhou), China (Shanghai), China (Qingdao), China (Beijing), China (Shenzhen), China (Guangzhou), China (Heyuan), China (Zhangjiakou), China (Ulanqab), China (Hong Kong), and Singapore

DAS Enterprise Edition V1

Database instance

Region

  • ApsaraDB RDS for MySQL

  • ApsaraDB RDS for SQL Server

  • PolarDB for MySQL

Note

ApsaraDB RDS for SQL Server 2008 R2 High-availability Edition is not supported.

China (Hangzhou), China (Shanghai), China (Qingdao), China (Beijing), China (Shenzhen), China (Zhangjiakou), China (Hohhot), China (Chengdu), China (Guangzhou), China (Heyuan), China (Ulanqab), China (Hong Kong), Singapore, Malaysia (Kuala Lumpur), and Indonesia (Jakarta)

ApsaraDB RDS for PostgreSQL

China (Hangzhou), China (Shanghai), China (Beijing), China (Shenzhen), China (Zhangjiakou), Singapore, Malaysia (Kuala Lumpur), and Indonesia (Jakarta)

PolarDB-X 2.0

China (Hangzhou), China (Shanghai), China (Beijing), China (Shenzhen), and Singapore

DAS Enterprise Edition V0

Database instance

Region

  • ApsaraDB RDS for MySQL

  • ApsaraDB RDS for SQL Server

  • PolarDB for MySQL

Note

ApsaraDB RDS for SQL Server 2008 R2 High-availability Edition is not supported.

China (Hangzhou), China (Shanghai), China (Qingdao), China (Beijing), China (Shenzhen), China (Zhangjiakou), China (Hohhot), China (Chengdu), China (Guangzhou), China (Heyuan), China (Ulanqab), China (Hong Kong), Singapore, Malaysia (Kuala Lumpur), Indonesia (Jakarta), Japan (Tokyo), US (Virginia), US (Silicon Valley), Germany (Frankfurt), and UK (London)

ApsaraDB RDS for PostgreSQL

China (Hangzhou), China (Shanghai), China (Beijing), China (Shenzhen), China (Zhangjiakou), Singapore, Malaysia (Kuala Lumpur), and Indonesia (Jakarta)

PolarDB-X 2.0

China (Hangzhou), China (Shanghai), China (Beijing), China (Shenzhen), and Singapore

DAS Cost-efficient Edition

Database instance

Region

  • ApsaraDB RDS for MySQL

  • PolarDB for MySQL

China (Hangzhou), China (Shanghai), China (Qingdao), China (Beijing), China (Shenzhen), China (Zhangjiakou), China (Chengdu), and China (Hong Kong)

DAS Basic Edition

Database instance

Region

  • ApsaraDB RDS for MySQL, PolarDB for MySQL, ApsaraDB MyBase for MySQL, and self-managed MySQL databases

  • ApsaraDB RDS for PostgreSQL, PolarDB for MySQL, and self-managed PostgreSQL databases

  • ApsaraDB RDS for SQL Server and ApsaraDB MyBase for SQL Server

  • PolarDB for PostgreSQL (Compatible with Oracle)

  • PolarDB-X2.0

  • ApsaraDB for Redis and self-managed Redis databases

  • ApsaraDB for MongoDB and self-managed MongoDB databases

All regions