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.
ImportantWith 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.
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 |
|
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.
|
V2 (formerly known as DAS Professional Edition of the new version) | Pay-as-you-go |
| |
V1 (formerly known as DAS Professional Edition of the previous version) | Subscription and pay-as-you-go |
| |
V0 (formerly known as DAS Professional Edition of the previous version that uses the previous link) | Pay-as-you-go |
|
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.
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 |
| 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 |
| 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 |
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 |
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 |
| China (Hangzhou), China (Shanghai), China (Qingdao), China (Beijing), China (Shenzhen), China (Zhangjiakou), China (Chengdu), and China (Hong Kong) |
DAS Basic Edition
Database instance | Region |
| All regions |