DMS is upgrading its metadata service to a cell-based architecture. For secure-access instances, this change processes metadata requests from the SQL window in the instance's region. This architecture provides low-latency, high-availability metadata access, significantly improving performance and user experience. This upgrade does not apply to unmanaged instances. Additionally, we are optimizing the display of some lists for faster loading speeds and a more streamlined interface.
Effective date
00:00:00 on February 11, 2026 (UTC+8)
What's changing
Backend service upgrade: Regional metadata request processing
To improve loading speed, services in the instance's region will handle metadata requests in the SQL window. This includes loading the Tables and programmable objects lists, as well as manual Refresh and sync metadata operations.
UI optimizations and simplifications
The programmable objects list: To improve loading performance for large datasets, the list will now use pagination instead of loading all data at once.
We are simplifying the menu in the upper-right corner (
icon) to focus on core information:Removed columns: We are removing the Favorite, Data Owner, and Permission Type columns from the list view. The Row-level Security field will also be removed from the details view.
Recommended action: To view or manage this information, go to the Actions column for the target table and then select .
Simplified paginator: We have removed the page jump feature. We recommend using the search function to quickly locate a specific table.
More actions for tables: We have removed the Change Data Owner menu item. If you need to change the data owner, use the Apply for Data Owner option to submit a request.
Impact and recommendations
This update consists of backend service optimizations and minor UI adjustments. It does not impact your daily workflows under normal circumstances.does
Supported engines:
RDS for MySQL, RDS for PostgreSQL, and RDS for SQL Server, self-managed MySQL, PostgreSQL, and SQL Server (including databases hosted on ECS, connected over the public network, through a VPC, or via a database gateway)
ApsaraDB for MongoDB, Tair (Redis OSS-compatible), and self-hosted MongoDB and Redis (including databases hosted on ECS, connected over the public network, through a VPC, or via a database gateway)
PolarDB for MySQL, PolarDB for PostgreSQL, PolarDB for Oracle, and PolarDB-X
AnalyticDB for MySQL and AnalyticDB for PostgreSQL
ApsaraDB for ClickHouse and self-managed ClickHouse (including databases hosted on ECS, connected over the public network, through a VPC, or via a database gateway)
Self-managed Oracle (including ECS self-managed, public network, VPC Express Connect, and Database Gateway access)
ApsaraDB for MariaDB and self-managed MariaDB (including ECS self-managed, public network, VPC Express Connect, and Database Gateway access)
Hologres
ApsaraDB for SelectDB and self-managed SelectDB (including ECS self-managed, public network, VPC Express Connect, and Database Gateway access)
Lindorm
Self-managed Hive and HANA (including ECS self-managed, public network, VPC Express Connect, and Database Gateway access)
Supported regions: China (Chengdu), China (Zhangjiakou), China (Beijing), China (Shanghai), China (Hangzhou), China (Shenzhen), China (Qingdao), China (Hong Kong), Singapore, China (Guangzhou), China (Ulanqab), Germany (Frankfurt), and Japan (Tokyo).