Convert SQL Server to IBM DB2.

Use our software for a seamless data migration or sync from any Microsoft SQL Server or Windows Azure SQL database to an IBM DB2 server. It is easy to use and effective. Our solution can convert and synchronize your whole dataset from MS SQL Server to an IBM DB2 target in just a few steps.

To perform a partial data transfer use our integrated data filters that are very useful when you need to convert/ sync only discrete tables. This is also useful for a partial data replication when you need to move, delete or insert only modified records.

Our applications reach the maximum possible conversion speeds so it saves your time and effort on the database transformation. A user-friendly interface and a wide range of features assist you by reducing manual efforts required for your conversion, getting your jobs done quickly and professionally.

So if you need to transfer databases in a heterogeneous environment or sync data between different platforms our solution will do the job automatically with minimum effort from you.

Built-in scheduler helps you to run any your task at a time that suits your preference.

Supported databases:
  • IBM DB2
  • Microsoft SQL Server
  • Microsoft SQL Azure
  • Amazon RDS
  • MS SQL Dump
 DBConvert for MSSQL & DB2

Version: 2.1.4

Release Date: Dec. 2, 2022

 DBSync for MSSQL & DB2

Version: 2.0.8

Release Date: Sept. 14, 2022

Try All-in-one DB migration and Sync software.

DBConvert Studio

 Version: 3.4.0

Release Date: May 17, 2023

Supported databases:

  • SQL Server
  • MySQL
  • MariaDB
  • Percona
  • Oracle
  • PostgreSQL
  • Access
  • FoxPro
  • SQLite
  • Interbase
  • Firebird
  • IBM DB2
  • MS Azure SQL
  • Amazon RDS
  • Amazon Aurora
  • Heroku Postgres
  • Google Cloud

Using SQL Server to IBM DB2 conversion and synchronization tools.

When you start DBConvert or DBSync application in GUI mode it guides you through several steps to set up the database migration or synchronization:

1. Connect to SQL Server source database.

If a source database requires you to log in, you can specify a user name/ password and host/ port parameters.

Connect to SQL Server source database from DBConvert

2. Connect to IBM DB2 destination database.

Specifying parameters for destination database looks like the same as for source. Usually, it consists of defining connection settings and username/password pairs.

Connect to IBM DB2 target database from DBConvert

NOTE #1: Every DBConvert or DBSync tool has two different databases in its name. That means any specified database from a pair can be set up as a source or destination. Besides, the same type of database may be set up both as a source or destination.

As an example, here is the list of possible migration directions with on-premises databases:

  • SQL Server to IBM DB2
  • IBM DB2 to SQL Server
  • SQL Server to SQL Server
  • IBM DB2 to IBM DB2

NOTE #2: Don't be confused by the fact that connections to cloud databases like Amazon RDS, Google Cloud, and Heroku are not explicitly specified in the configuration of a source or destination in the DBConvert / DBSync interface. To connect to Cloud database instances, use the same settings as you do for traditional on-premises databases.

NOTE #3: Your connections to source and target databases stay active until you close DBConvert/ DBSync application or reopen new connections on "source" and "destination" steps.

Read more about the specific source/ destination configurations for different databases.

3. Configure database migration options.

At the next step, you can specify precisely which tables, fields, indices, views you want to transfer to the IBM DB2 destination database. Just check/ uncheck the box in front of each database object you want to convert.

Customize general database/ tables settings. Or set up a particular table , field, index individually when migrating data from SQL Server to IBM DB2.

Check out our articles about Configure database migration options. for detailed information.

The screenshot below sums up general features available in DBConvert software solutions.

4. Detection of potential database migration issues. Errors and Warnings

The database typically constrains certain relations on the data that cannot be violated. On the customization step, a smart error checker verifies all possible Data integrity and Referential integrity issues and highlights them, if any, before performing a migration.

By default, DBConvert tries to automatically map the database types of the source SQL Server database to the closest equivalent of the target IBM DB2 database types. However, you can manually change the data types for the entire database globally using the "Global mapping" or individually for each field.

Check out Smart error checker. Errors and Warnings for more information.

5. Execution. The final stage of data migration from SQL Server to IBM DB2

Once you configure source and destination databases for migration in the previous steps, you can start the actual conversion or synchronization process.

Click the "Commit" button to start conversion. Also, here, you can monitor the migtation/ synchronization process.

Optionally save connection settings and configuration parameters into the session file to schedule the launching of sync or migration jobs regularly.

Execution step of DBConvert products

Read more about execution stage available options.

Command line mode

Previously saved sessions can be passed as parameters to Command-Line DBConvert Client. A session keeps SQL Server source and IBM DB2 target database connection settings with other specified options.

Example: C:\Program Files\DBConvert\mssql2db2Pro\mssql2db2Pro_Cons.exe /Session:"Session_Name"

NOTE: First, you have to run the software in GUI mode to create a session file with initial parameters.

Built-in scheduler.

Our applications come with a built-in scheduler to run database migration and sync jobs at specified times. Just set the scheduled date and time to execute job sessions automatically.

Find more Information about built-in scheduler

DBConvert screenshot

Supported OS:

Requirements

  • Microsoft Visual C++ 2008 x86 Redistributable package
  • Necessary privileges to write into empty database on the target DB2 server
  • If you connect to remote DB2 server that IBM Data Server Client should be installed on the machine where our tool is installed. You can download this client here: https://www-01.ibm.com/support/docview.wss?uid=swg21385217
  • Necessary privileges to write into database on the target SQL Server (this requirement is optional as there is an option to overcome the restrictions using dump file)

Related Links

Highlights

Read information about reverse migration.