DB2Migrator^™

Try 2-day free fully functional trial version
of DB2Migrator

Looking for a safe way to migrate your data from DB2 to SQL Server?

This simple, but very powerful tool is exactly what you need!

Overview

DB2Migrator is an effective assistant for DB2 to SQL Server 2008/2012 data migration. The tool transfers data from DB2 tables to existing SQL Server tables in a few easy steps. It is simple in use and advantageous in work.

Attention

Free trial version of DB2Migrator can be used for evaluation purposes during 2 days after the downloading. Also, it migrates 10% of rows per each table, but not less than 100 rows. To enjoy full functionality of this product for unlimited period of time, you must buy a license.

How to use the tool

Execute the DB2MigratorSetup.msi file after it has been downloaded. During the installation, you should specify the folder for the program files and choose features to be installed. If you check “Launch DB2Migrator when setup exits” during the installation, DB2Migrator wizard will be opened. Now you can start the migration!

Gordan R., Telecom Company

This tool has migrated our database in just 1 day, while we were focusing on more important things.

Features

An interface is in a form of wizard which allows restarting migration from any step;

The tool uses the bulk copy mechanism to load data from DB2 tables to SQL Server. This approach allows to achieve the maximum possible insertion speed;

You can edit the SELECT statement which reads the source data. This allows fixing many common data migration problems like incompatibilities in data types. Besides, it makes possible to perform a partial data migration, when you need to move only a definite range of records;

By creating a single migration task, you can migrate many tables at once. The target SQL Server database and schema can be specified only once for the whole task;

DB2Migrator has a Column Mapping feature, which allows establishing a custom correspondence between DB2 and SQL Server columns if necessary. This can occur, for example, when a DB2 column name happens to be a SQL Server keyword;

Current migration task can be saved in a file and restored later. Thus you don't need to specify all parameters from scratch when you are repeating the migration for a similar set of tables on the same servers.