Migrating data from IBM DB2 to SQL Azure

This guide walks you through migrating data from IBM DB2 to SQL Azure in a few simple steps using ESF Database Migration Toolkit. Simplify complex migration tasks and save valuable time with our streamlined approach.

IBM DB2 vs. SQL Azure:

IBM DB2 is a high-performance relational database management system (RDBMS) developed by IBM, designed to handle large volumes of data and support complex transactions. It offers robust features for data management, security, and scalability, making it suitable for enterprises of all sizes. DB2 is known for its efficiency in processing SQL queries, its advanced analytics capabilities, and its integration with various platforms, including cloud environments. It supports a range of operating systems such as Windows, UNIX, and Linux, and provides tools for database automation, optimization, and administration.
Microsoft SQL Azure, also known as Azure SQL Database, is a fully managed relational database service provided by Microsoft. It offers scalable and high-performance SQL database capabilities in the cloud, with built-in high availability, automated backups, and robust security features. Designed to handle both small and large-scale applications, Azure SQL Database simplifies database management tasks, allowing developers to focus on building applications without worrying about underlying infrastructure. It supports various deployment options, including single databases, elastic pools, and managed instances, catering to diverse business needs.

Prerequisite:

Software Required:

DMToolkit_x64.zip (63.5 MiB)	64-bit Windows application for ESF Database Migration Toolkit 12.2.09 (2025-07-17). (md5: af00d640b9e71618ed20932c52f4688d)
DMToolkit_win32.zip (58.8 MiB)	32-bit Windows application for ESF Database Migration Toolkit 12.2.09 (2025-07-17). (md5: 1b7566ee53ff21b6dc8444741b9da73a)

System Supported:
- Windows 7 or higher.
- IBM DB2 9.x or higher.
- SQL Azure.

Step by Step Wizard:

Connect to IBM DB2
- In the "Choose a Data Source" dialog:
  - Select "IBM DB2"
- Specify server connection details:
  - Server name: localhost (default)
  - Port: 50000 (default)
- Enter authentication credentials:
  - Username: db2admin (default)
  - Password
- In the Database combobox:
  - Enter the source DB2 database name
- Schema selection procedure:
  1. Click Refresh Schema to load available schemas
  2. Select desired schema from the list
Fig. 1: IBM DB2 data source configuration
Configure SQL Azure Data Destination
- Prerequisite:
  - Enable access in Azure server's "Firewalls and virtual networks" page
  - Add your client IP to the firewall rules
- In the "Choose a Destination" dialog:
  - Select "SQL Azure"
- Enter server details:
  - Server name: e.g., esf.database.windows.net
  - Port: 1433 (default)
- Provide authentication credentials:
  - Username and password
- Database selection:
  - Click Refresh Database to load databases
  - Select target database
- Schema selection:
  - Click Refresh Schema to load schemas
  - Choose existing schema (dbo schema is default)
Fig. 2: SQL Azure data destination configuration
In "Select Source Table(s) & View(s)" Dialog
- Select migration objects: Choose tables or views to include in the migration.
  
  Fig. 3: Select tables and views
- Modify table structure: Click the ellipsis (...) button to access table options and schema adjustments.
  
  Fig. 4: Do transform
- Configure field mapping: In the Field Mapping options:
  - Customize destination fields (name, data type, default value, comments)
  - Select data transfer method:
    - Overwrite Table (replace existing data)
    - Empty Data (truncate before insert)
    - Append Data (add to existing data)
    - Skip Table (exclude from transfer)
  - Apply data filters before transfer
Execution Dialog
- Start migration: Click "Submit" to initiate automated data transfer from IBM DB2 to SQL Azure.
  
  Fig. 5: Execute migration
- Monitor progress: Click "Browse Log" for real-time migration tracking, including issue resolution details.
- Save configuration: Click "Save as job" to store settings for:
  - Quick reloads of migration jobs
  - Command-line execution (use: dmtc.exe --help for parameter options)
Finished!

After migration completes, the toolkit generates a comprehensive report for verifying migration accuracy. You can monitor progress as the automated process runs efficiently. For any questions or feedback, contact us – our team is ready to assist.