Seamless Migration: Move from IBM DB2 LUW to Microsoft SQL Server

Table of Contents

1. Introduction
2. SQLWas Wizard
   • Welcome to the SQLWAS Wizard page
   • Choosing the Source Database
   • Choosing the Target Database
   • Advanced Options
   • Object Selection
   • Data and DDL Options
   • Specify Export File Options
   • Specify Import Options
   • Review the Selection
   • Conversion Process
3. SQL Studio
   • Using SQL Studio
4. SQL Was Commander
   • Using SQL Was Commander
5. Conclusion

Introduction

In this article, we will discuss various ICE P tools that assist in migrating from DB2 Linux Unix Windows to Microsoft SQL Server. We will explore three graphical tools provided by IAR Systems for database migration and conversion: SQLWas Wizard, SQL Studio, and SQL Was Commander.

SQLWas Wizard

The SQLWas Wizard is a tool that works with a DB2 database using an ODBC connection. It allows users to connect to a DB2 database and convert both data and definitions to a SQL Server database. The wizard guides users through the entire migration process. Let's take a closer look at the different steps involved in using the SQLWas Wizard.

Welcome to the SQLWas Wizard page

When launching the SQLWas Wizard, users are greeted with a welcome page that allows them to select a project directory or Create a new one. The project directory is where all the conversion definitions and objects will be stored. This information can be reused for future runs of the wizard.

Choosing the Source Database

On the "Choose Source Database" page, users need to specify the ODBC DSN (Data Source Name) for their DB2 database. This can be a system DSN, user DSN, or even a file DSN. Additionally, the username and password for the DB2 database must be provided. It is recommended to use an administrator user with appropriate privileges for a successful export.

Choosing the Target Database

Next, on the "Choose Target Database" page, users need to specify the target database as Microsoft SQL Server. The version can be selected from the list of supported versions. Users can choose to use either SQL authentication or Windows authentication for the SQL Server database.

Advanced Options

The "Advanced Options" page allows users to specify the bin directory where the native tools for data and definition loading into the SQL Server database reside.

Object Selection

All the objects extracted from the DB2 database, such as tables, views, stored procedures, triggers, user-defined types, sequences, and synonyms, are displayed in a tree view on the "Object Selection" page. Users can filter the objects Based on specific criteria, such as schema name, and select or remove objects for conversion.

Data and DDL Options

On the "Data and DDL Options" page, users can configure various options for the conversion process. This includes choosing whether to convert schema names, SQL scripts, or both. Users can also define global or local data Type mappings and specify whether to export data, definitions, or both during the conversion process. These options provide flexibility and control over the migration process.

Specify Export File Options

The "Specify Export File Options" page allows users to specify the export directory where all the intermediate files generated during the conversion process will be stored. These files contain SQL statements, batch commands, and format files for data loading. Additionally, log files and error files are also generated for analysis and troubleshooting.

Specify Import Options

On the "Specify Import Options" page, users can specify whether to use a client installed on the Current computer or import the files to another computer in the network for execution. This provides flexibility and convenience in managing the import process.

Review the Selection

The "Review the Selection" page provides a summary of the selected options and settings before initiating the conversion process. Users can review their choices and make any necessary changes before proceeding.

Conversion Process

Once all the configurations are finalized, the SQLWas Wizard starts the conversion process. The tool begins by extracting and converting all the specified objects, including tables, views, stored procedures, triggers, and user-defined types. The data and definitions are transformed into SQL Server syntax. The conversion process is divided into extraction and import phases. The extraction phase extracts the data and definitions, while the import phase loads the converted data and definitions into the SQL Server database. A progress log displays information about the migration process, allowing users to monitor the status and ensure a successful conversion.

SQL Studio

SQL Studio is another tool provided by IAR Systems for database migration. Unlike the SQLWas Wizard, SQL Studio is designed to work with individual scripts. Users can copy the script in DB2 syntax to the left pane of SQL Studio, specify the source as DB2, and the target as SQL Server. The tool then converts the script from DB2 to SQL Server syntax. SQL Studio is a simple and intuitive tool that allows users to quickly convert scripts and review the results.

SQL Was Commander

SQL Was Commander is another powerful tool for script conversion. Similar to SQL Studio, SQL Was Commander supports the conversion of individual scripts. However, it also provides the ability to work with multiple scripts simultaneously. Users can specify a set of scripts or an entire folder for conversion. SQL Was Commander utilizes the SQLWas tool in command-line mode to convert the scripts from DB2 to SQL Server. The tool provides a comprehensive log that displays information about the conversion process and allows users to compare the source and target results side by side.

Conclusion

In this article, we explored three powerful tools provided by IAR Systems for database migration and conversion: SQLWas Wizard, SQL Studio, and SQL Was Commander. These tools offer a user-friendly interface and comprehensive features for extracting data and definitions from a DB2 database and converting them to a SQL Server database. Whether You need to migrate an entire database or convert individual scripts, these tools provide the flexibility and functionality to successfully complete the conversion process. With their intuitive design and robust functionality, these tools are a valuable asset for any database migration project.