Metadata is used to retrieve and display data in Data Management (DMS). Metadata is the basis for automatic identification based on sensitive data rules. Metadata can also be used to implement fine-grained access control on databases, tables, columns, rows, and programmable objects. DMS supports different metadata collection scopes and methods based on the control mode of each database instance.
Background information
Metadata is a type of data dictionary that describes a database. Metadata includes the database name, the database character set, table names, table sizes, the number of rows in each table, the character set of each table, table columns, table indexes, the description of each table, the data type of each column, the precision of the columns, and the description of the columns. DMS collects metadata from databases such asinformation_schema
. The collected metadata may not be accurate and is used only for reference. Collection scopes and methods
Collection scope and method | Security Collaboration | Stable Change and Flexible Management |
---|---|---|
Metadata collection scope | DMS collects and stores all metadata of a database instance. For more information, see the Collected metadata section of this topic. | DMS collects and stores all metadata of a database. Other metadata is loaded in real time after logon. |
Full metadata collection at the point in time when a database is added to DMS | Supported. | Supported. |
Full metadata collection at specified points in time | By default, DMS collects metadata from all instances that are managed in Security Collaboration mode of a tenant at six points in time each day. Note DMS synchronizes the metadata every four hours at 02:00, 06:00, 10:00, 14:00, 18:00, and 22:00. | Not supported. |
On-demand incremental metadata collection |
|
|
Others | N/A | When you log on to a database, DMS collects information about the database based on the permissions of the account that you use. |
Use metadata
Collected metadata
Object | MySQL series (1) | PostgreSQL series (2) | SQL Server | Oracle | MongoDB | Redis |
---|---|---|---|---|---|---|
Database |
| Name | Name | Name | N/A | Name |
Table |
|
|
|
| N/A | N/A |
Column |
|
|
|
| N/A | N/A |
Index |
|
|
|
|
| N/A |
Programmable object |
|
|
| N/A | N/A | N/A |
Schema | N/A | Name | N/A | N/A | N/A | N/A |
Collection | N/A | N/A | N/A | N/A | Name | N/A |
Key | N/A | N/A | N/A | N/A | N/A |
|
(1) Native MySQL, PolarDB for MySQL, PolarDB for Xscale, AnalyticDB for MySQL, Data Lake Analytics (DLA), ApsaraDB for ClickHouse, ApsaraDB OceanBase for MySQL, native MariaDB, and ApsaraDB RDS for MariaDB
(2) Native PostgreSQL, PolarDB for PostgreSQL(Compatible with Oracle), PolarDB for PostgreSQL, AnalyticDB for PostgreSQL, and ApsaraDB OceanBase for Oracle.