Data Management (DMS) provides the database export feature. You can use this feature to export an entire database or specific tables in the database for data analysis.
Prerequisites
One of the following types of databases is used:
- MySQL: self-managed MySQL, ApsaraDB RDS for MySQL, PolarDB for MySQL, PolarDB-X, AnalyticDB for MySQL, and ApsaraDB OceanBase for MySQL
- SQL Server: self-managed SQL Server and ApsaraDB RDS for SQL Server
- PostgreSQL: self-managed PostgreSQL, ApsaraDB RDS for PostgreSQL, PolarDB for PostgreSQL, and AnalyticDB for PostgreSQL
- PolarDB for Oracle
- MariaDB
Note For more information, see Supported database types and features.
Procedure
Usage notes
- After you submit a data export ticket for approval, you can close the ticket regardless of whether the ticket is approved or rejected. This reduces data exposure.
- Approval rules are configured by DMS administrators and DBAs. If you are a DMS administrator or DBA, click Security and Specifications in the top navigation bar of the DMS console. Then, click Security Rules in the left-side navigation pane to configure approval rules for data export tickets. We recommend that you submit tickets to export data in the test environment. This way, affected rows can be checked and a backup file can be created for each data export. This also allows you to restore data when the data export does not work as expected. To ensure high R&D efficiency, you can specify that no approval is required for data export tickets in the test environment.