Data Management Service (DMS) automatically collects the data dictionary of your database instances, reading structure information from the actual database and keeping the metadata view in DMS up to date. If the metadata in DMS is out of sync with your database, manually trigger a sync.
How it works
A data dictionary supports hierarchical permission management across databases, tables, fields, and programmable objects. When DMS collects the data dictionary, it reads the following:
Database level: Names and character sets of databases.
For instances in Security Collaboration control mode, DMS ignores system databases by default. See System databases that are ignored by DMS by default.
Table level: Names, occupied storage space, row count, character sets, fields, indexes, and descriptions.
Field level: Types, precision, and descriptions.
DMS syncs the data dictionary automatically when you change a schema in DMS. If you change a schema outside DMS, sync the data dictionary manually.
For background on data dictionaries, see Metadata.
Prerequisites
Before you begin, make sure you have:
The DBA or administrator system role. To check your role, see View my system roles.
Sync a data dictionary
Choose either method. Both open the same Sync Dictionary dialog box.
Method 1: Via the instance list
Log on to the DMS console V5.0.
In the top navigation bar, choose Data Assets > Instances.
In simple mode, move the pointer over the
icon in the upper-left corner and choose All Features > Data Assets > Instances.Click the Instance List tab.
In the Actions column of the target instance, click More > Refresh/Sync Dictionary.
In the Sync Dictionary dialog box, click OK.
Method 2: Via right-click
Log on to the DMS console V5.0.
Right-click the target instance in the instance list on the left and select Refresh/Sync Dictionary.
In the Sync Dictionary dialog box, click OK.
FAQ
DMS metadata synchronization is slow. After I manually sync the data dictionary, I still cannot see a newly created database or table. What should I do?
Diagnose by scenario:
The database does not appear after the sync completes: The database account used by DMS may lack access permissions for the new database. On RDS SQL Server instances, permissions are not automatically granted to the account by default when a new database is created. To grant the required permissions:
Log on to the ApsaraDB RDS console and click Instances in the left navigation pane.
In the top menu bar, select the destination region.
Find the target instance and click its ID to open the Basic Information page.
In the left navigation pane, click Accounts.
Locate the database account used by DMS. In the Actions column, click Modify Permissions or Reset Account Permissions to grant the required privileges on the new database.
The sync is taking a long time: The instance contains many databases and tables, which makes metadata synchronization time-consuming. The sync duration is proportional to the number of databases and tables in the instance. A sync task can take several minutes or longer to complete. Wait for the task to finish.