Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

CUBRID Migration Toolkit v2013.05 Released

DZone's Guide to

CUBRID Migration Toolkit v2013.05 Released

· Database Zone
Free Resource

Traditional relational databases weren’t designed for today’s customers. Learn about the world’s first NoSQL Engagement Database purpose-built for the new era of customer experience.

We are glad to announce the release of a new version 2013.05 of CUBRID Migration Toolkit which allows to migrate or extract existing data and/or schema from MySQL/Oracle/CUBRID (previous versions) to the latest version of CUBRID Database Server, and perform scheduled execution of batch operations.

You can download CMT binaries for Windows, Linux, and Mac OS X from http://www.cubrid.org/?mid=downloads&item=cubrid_migration_toolkit&os=detect&cubrid=any.

In this release many UI improvements for the Migration Wizard have been made. We have added the migration type selection (Figure 1) as the first step of migration process. This improves the UX when starting a new migration.

cmt_migration_type_selection.png

Figure 1: Select Migration Type.

Before, it was possible to run one migration process at a time. The inconvenient part of this fact was that a user could create another migration script only after the previous one has been completed. Now CMT allows to schedule migration tasks even if there are running processes (Figure 2).

cmt_schedule_migration.png

Figure 2: Schedule migration instead of starting.

When scheduling a migration task users are given an option to select a particular date and time to start the migration task, a time of the day for recurring tasks, or supply a UNIX compatible cron job scheduling pattern (Figure 3).

cmt_schedule_date.png

Figure 3: Migration Schedule Settings.

In the new version of CMT, users can rerun the migration script if any failure has occurred during migration (Figure 4). This allows users to avoid going through the creating of the mgiration script all over again.

cmt_rerun_script_on_failure.png

Figure 4: Rerun the migration script upon failure.

In addition to this, users can go back to Migration History tab, choose one of the previously executed tasks and rerun it again (Figure 5).

cmt_migration_history.png

Figure 5: Migration History.

We hope these improvements will provide a better user experience when performing the migration process.

To see the full list of changes, refer to CMT Release Notes.


CUBRID 8.4.3 - Faster and More Stable

Learn how the world’s first NoSQL Engagement Database delivers unparalleled performance at any scale for customer experience innovation that never ends.

Topics:

Published at DZone with permission of Esen Sagynov, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}