IBM DB2
SQL Server

IBM DB2 to SQL Server Converter

Move IBM DB2 data into SQL Server, Azure SQL, Azure SQL Managed Instance, or Amazon RDS for SQL Server with schema conversion, type mapping, saved sessions, and optional two-way sync.

DBConvert moves IBM Db2 data into SQL Server through a desktop wizard with schema selection, type-mapping review, saved sessions, and optional DBSync when the cutover has to happen in stages.

DBConvert connects to IBM Db2 through IBM Data Server Client libraries and reads selected schemas, tables, fields, indexes, views, foreign keys, and data, then creates SQL Server-compatible tables on SQL Server, SQL Server Express, Azure SQL Database, Azure SQL Managed Instance, or Amazon RDS for SQL Server, with the type mapping reviewed before the transfer runs.

  • Saved sessions, filters, and scheduler / CLI runs make the load repeatable, and DBSync keeps both systems aligned during rollout.

Which tool: DBConvert or DBSync?

Use DBConvert for a planned Db2 to SQL Server migration; use DBSync when Db2 must keep changing while SQL Server is introduced in stages.

DBConvert for Db2 → SQL Server

One-time conversion with Db2 connection settings, schema and table selection, type-mapping review, data filters, saved sessions, and SQL Server dump output when a DBA-controlled restore is preferred.

DBSync during a Db2 → SQL Server cutover

Keep Db2 changes flowing into SQL Server while SQL Server takes over application traffic. Define table ownership and conflict rules before enabling any return flow; see database synchronization concepts.

Need more context? Compare DBConvert and DBSync side by side →

How DBConvert handles the Db2 → SQL Server differences

DBConvert handles the table-level migration in the wizard: connection, schema selection, type mapping, transfer, and validation. SQL PL and application SQL remain a separate rewrite track.

Connection and schema

DBConvert connects through IBM Data Server Client libraries, then reads the selected Db2 schema: tables, fields, indexes, views, foreign keys, and rows.

Type mapping review

DBConvert exposes Db2-to-SQL-Server column mappings before the target tables are created, so precision, Unicode, LOB, and DATETIME2 decisions are explicit.

Keys and generated values

Identity columns and standalone sequences are loaded with the data. After import, confirm next values before SQL Server resumes writes.

Application SQL cleanup

Db2-specific SQL such as global variables, || concatenation, and FETCH FIRST pagination needs a T-SQL review outside the table copy.

Validation after import

DBConvert compares source and target row counts after the load. Follow with key-range, nullable-column, LOB, and timestamp spot checks.

Procedural code boundary

DBConvert migrates tables, views, and foreign keys. SQL PL procedures, triggers, modules, global variables, and embedded application SQL are rewritten manually in T-SQL.

SQL PL routines and application code - out of scope

DBConvert's migration covers tables (with their fields, types, defaults, and indexes), views, and foreign keys. Db2 SQL PL stored procedures, triggers, global variables, COBOL jobs, and embedded application SQL stay in the source and are rewritten manually in T-SQL - treat procedural code as a conversion track running beside the schema and data migration.

Type mapping checkpoints

Review these columns first when the source schema mixes Db2 OLTP tables with reporting or legacy application data.

Db2 source type SQL Server target type Migration note
DECIMAL(p,s), NUMERIC(p,s) DECIMAL(p,s) Keep declared precision and scale; review finance columns before shortening.
DECFLOAT FLOAT or DECIMAL Pick approximate or fixed precision per column; do not leave the choice implicit for money values.
GRAPHIC, VARGRAPHIC NCHAR, NVARCHAR Use Unicode targets so double-byte character data survives the move.
CLOB, DBCLOB, BLOB NVARCHAR(MAX), VARBINARY(MAX) Sample the largest rows after load; LOB columns often reveal timeout or driver issues first.
TIMESTAMP DATETIME2 Prefer DATETIME2 over legacy DATETIME for broader range and fractional-second precision.
Identity columns, sequences IDENTITY, SEQUENCE Confirm next values after load so new SQL Server inserts do not collide with migrated keys.

Choosing the migration route

Pick the route by project shape: repeatable desktop conversion, Microsoft-native assessment, SQL Server ETL, enterprise replication, or code translation.

Route Where it fits Where it falls short
DBConvert commercial desktop conversion, Windows Schema and data migration with Db2 connection setup, table selection, type mapping, filters, saved sessions, SQL Server / Azure / RDS targets, and SQL dump output. Commercial license; desktop tool. Db2 SQL PL, COBOL jobs, and application SQL are outside DBConvert's scope.
DBSync commercial desktop synchronization, Windows Staged Db2 → SQL Server rollout while Db2 remains the changing source until the final switch. Requires clear table ownership and conflict rules; not a stored-procedure or application-SQL converter.
SSMA for Db2 Microsoft Migration Assistant, free Microsoft's official path for one-time Db2 user-database migrations into SQL Server or Azure SQL. Microsoft-native workflow; no DBSync-style staged synchronization, no SQL dump delivery, and still requires review for DB2 SQL PL and application SQL.
SSIS or linked-server ETL Microsoft data pipeline Data-only movement when the organization already maintains SSIS packages or SQL Server jobs around the target warehouse. No schema conversion workflow, no pair-specific type-mapping review, and no packaged desktop wizard for business users.
Enterprise CDC / replication tools low-downtime replication Long parallel-run projects where Db2 changes must stream into SQL Server with low downtime and dedicated operations staff. A replication program, not a schema-and-data conversion wizard; stored code, type mapping, and application SQL still need a migration track.
SQL/code conversion specialists DDL, SQL PL, embedded SQL Projects where the hard part is translating stored procedures, triggers, functions, modules, or application SQL into T-SQL. A different problem from copying live table data, saving repeatable jobs, or keeping Db2 and SQL Server synchronized during rollout.

Supported versions and services

IBM DB2

  • IBM DB2 v9.7 and later

SQL Server

  • SQL Server 2008-2022, including Express editions
  • Azure SQL Database and Amazon RDS for SQL Server
  • SQL Server schemas (dbo, custom schemas)
  • Windows authentication or SQL authentication
IBM DB2

All IBM DB2 Tools

Other directions and pairs
SQL Server

All SQL Server Tools

Migration & sync options

Reverse Conversion

SQL Server to IBM DB2

DBConvert Studio

30+ databases · cloud · scheduled sync

Need more directions or unattended sync? One tool covers them all.

How to migrate IBM DB2 to SQL Server

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

1

Connect to IBM DB2 source database

Specify the username/password and host/port parameters if your source database requires login credentials.

Connect to IBM DB2 source database from DBConvert

DB2 source

Connect through IBM Data Server Client libraries — select the source DB2 schema in the wizard.

2

Connect to SQL Server destination database

Specify parameters for the destination database similar to the source, defining connection settings and username/password pairs.

Connect to SQL Server target database from DBConvert

SQL Server target

Connect by TCP/IP or Named Pipes, use Azure SQL, or configure Amazon RDS for SQL Server.

Steps 3-6: the same for every database pair

Source and target are connected - steps 1 and 2 above. What follows is identical whichever two databases you picked, so it lives in one place. Each step below opens at its own section.

Open the full guide

All four steps in one page, plus software features, command-line mode, scheduler, and system requirements.

See all features

More guides for IBM DB2 ↔ SQL Server