Open Source RDBMS - Seamless, Scalable, Stable and Free

한국어 | Login |Register

New Features of CMT

New Features of CMT

1.    Manage scripts with group view


Users can choose which view will be displayed: Item view will list all of the migration scripts directly and Group view will display the groups of every migration scripts.

Users can use “Group Settings” to add/edit/delete the groups and which script belongs to a specified group.

If the amount of the migration script is big, the group view is very useful.

And users can do some Dragging and Dropping actions in the migration script list view to adjust the script items’ group or displaying order.


Note: The “Default Group” can’t be deleted and edit. All of the new scripts belong to the “Default Group”

2. Multi-Schema migration supported


If source database is Oracle or MSSQL, CMT supports migrating multi-schema in once migration process.

All of the schemas which the user can access in source database will be listed in the object mapping page and users can choose which object they want to migrate.


Note: Choosing a right user to connect the source database to avoid CMT fetching too many schemas from source database. For example: Using “sa” to connect a MSSQL database is not a very good practice if there are too many schemas in the source database and users just want to migrate only one schema.

3. CSV parser’s “Escape Mode” will be empty by default


In the old version, the “Escape Mode” is ‘\’ by default, and since this version, an empty char will be the default value of this option.


4. Information dialog after object mapping page


All of the warnings and confirmations about object mapping will be listed in above dialog before users go to the last stage of migration wizard.


5. Known Issues of CMT

1. MSSQL’s data type “hierarchyid” can’t be supported by CMT now. So the columns with this type will be ignored during migration.

2. Please pay more attention about tables mapping if there are more than one schemas in source database. CUBRID doesn’t support multi-shemas under one database user, so the tables with same name and from different schemas of source database will be mapped to the same table of the target CUBRID database by default.



comments powered by Disqus
Page info
viewed 6814 times
translations en
posted 3 years ago by
updated 3 years ago by
View revisions
Share this article