Database Autonomy Service (DAS) is available in three editions — Basic, Economy, and Enterprise — each building on the features of the previous tier. This topic describes what each edition includes, which database engines are supported, and which regions are available.
DAS editions
Each higher edition includes all features from lower editions.
DAS Basic Edition — Free. Provides centralized management across multiple database engines, along with diagnostics and performance optimization tools for day-to-day database O&M.
DAS Economy Edition — Paid. Adds lightweight autonomy features on top of Basic, including automatic tablespace fragment recycling, performance insight (new version), and enhanced versions of session management and lock analysis.
Note DAS Economy Edition is released in phases. For details, see [Notice] Renaming of DAS Professional Edition to DAS Enterprise Edition and release of DAS Economy Edition and DAS Enterprise Edition V3.DAS Enterprise Edition — Charged on a pay-as-you-go basis. Adds SQL Explorer and Audit on top of Economy. DAS Enterprise Edition V3 supports hybrid storage of hot and cold data and per-feature billing for flexible cost control. Compared with similar services in the Chinese mainland, DAS Enterprise Edition V3 reduces costs by 20%. Compared with similar services outside the Chinese mainland, DAS Enterprise Edition V3 reduces costs by more than 80%.
ImportantDAS Enterprise Edition V0, V1, and V2 are no longer available for new database instances, and DAS Enterprise Edition V1 cannot be upgraded. Migrate from V1 or V2 to V3 free of charge — billing continues under the original version's rules until migration completes, then switches to V3 rules. For billable item details by version, see Billing details.
Note DAS Professional Edition has been renamed to DAS Enterprise Edition. For details, see [Notice] Renaming of DAS Professional Edition to DAS Enterprise Edition and release of DAS Enterprise Edition V3.
Supported databases and regions
If your database instance is not deployed in a supported region, submit a ticket for technical support. Alibaba Cloud will assess feasibility and respond within 5 business days.
| Edition | Supported database | Supported region |
|---|---|---|
| DAS Enterprise Edition V3 | ApsaraDB RDS for MySQL, PolarDB for MySQL | Alibaba Cloud Public Cloud: China (Hangzhou), China (Shanghai), China (Qingdao), China (Beijing), China (Shenzhen), China (Heyuan), China (Zhangjiakou), China (Hohhot), China (Chengdu), China (Guangzhou), China (Ulanqab), Indonesia (Jakarta), US (Virginia), US (Silicon Valley), Japan (Tokyo), Germany (Frankfurt), UK (London), Philippines (Manila), Malaysia (Kuala Lumpur), Singapore, and China (Hong Kong) Alibaba Finance Cloud: China East 1 Finance, China East 2 Finance, China North 2 Finance (invitational preview), and China South 1 Finance |
| ApsaraDB RDS for PostgreSQL | Alibaba Cloud Public Cloud: China (Hangzhou), China (Shanghai), China (Qingdao), China (Beijing), China (Zhangjiakou), China (Hohhot), China (Ulanqab), China (Shenzhen), China (Heyuan), China (Guangzhou), China (Chengdu), US (Virginia), US (Silicon Valley), UK (London), Japan (Tokyo), Germany (Frankfurt), Malaysia (Kuala Lumpur), Indonesia (Jakarta), Thailand (Bangkok), Singapore, and China (Hong Kong) Alibaba Finance Cloud: China East 1 Finance, China East 2 Finance, and China South 1 Finance | |
| ApsaraDB RDS for SQL Server | Alibaba Cloud Public Cloud: China (Hangzhou), China (Shanghai), China (Shenzhen), China (Heyuan), China (Guangzhou), China (Qingdao), China (Beijing), China (Zhangjiakou), China (Hohhot), China (Ulanqab), China (Chengdu), US (Virginia), US (Silicon Valley), UK (London), Japan (Tokyo), Germany (Frankfurt), Malaysia (Kuala Lumpur), Indonesia (Jakarta), Singapore, and China (Hong Kong) Alibaba Finance Cloud: China East 1 Finance, China East 2 Finance, China North 2 Finance (invitational preview), and China South 1 Finance | |
| PolarDB-X 2.0 Note PolarDB-X 2.0 is also known as PolarDB for Xscale 2.0. In this topic, this service is referred to as PolarDB-X 2.0. | Alibaba Cloud Public Cloud: China (Hangzhou), China (Shanghai), China (Shenzhen), China (Beijing), China (Zhangjiakou), and China (Hong Kong) Alibaba Finance Cloud: China East 1 Finance, China East 2 Finance, China North 2 Finance (invitational preview), and China South 1 Finance | |
| PolarDB for PostgreSQL, PolarDB for PostgreSQL (Compatible with Oracle) | China (Hangzhou), China (Shanghai), China (Shenzhen), China (Beijing), China (Zhangjiakou), and China (Hong Kong) | |
| DAS Enterprise Edition V2 | 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 | ApsaraDB RDS for MySQL, ApsaraDB RDS for SQL Server (except 2008 R2 High-availability Edition), PolarDB for MySQL | 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 | ApsaraDB RDS for MySQL, ApsaraDB RDS for SQL Server (except 2008 R2 High-availability Edition), PolarDB for MySQL | 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 Economy Edition | 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 | ApsaraDB RDS for MySQL, PolarDB for MySQL, ApsaraDB MyBase for MySQL, and self-managed MySQL database ApsaraDB RDS for PostgreSQL, PolarDB for PostgreSQL, and self-managed PostgreSQL database ApsaraDB RDS for SQL Server and ApsaraDB MyBase for SQL Server PolarDB for PostgreSQL (Compatible with Oracle) PolarDB-X 2.0 Tair (Redis OSS-compatible) and self-managed Redis database ApsaraDB for MongoDB and self-managed MongoDB database | All regions |
Supported features
The following symbols are used in the feature tables:
✔️ — Supported
➖ — Not applicable
❌ — Not supported
What's next
For features supported by each database engine, see Supported database engines and features.
To enable DAS Economy Edition or DAS Enterprise Edition, see Enable and manage DAS Economy Edition and DAS Enterprise Edition.
Note DAS Basic Edition is enabled automatically when you connect a database instance to DAS. For details, see Connect a database instance to DAS.To migrate between DAS Enterprise Edition versions, see the How do I migrate data between different versions of DAS Enterprise Edition? section in the FAQ.