Demo presentation text:
Let me show you a Demo Presentation of the tools provided by Ispirer Systems for migration of database objects and sql scripts from DB2 iSeries to Sybase ASE.
First of all, I’d like to mention that Ispirer Systems provides tools and services for automating database and application migration processes for a variety of conversion directions. The list of tools supplied for such a kind is as follows:
• SQLWays Wizard – a GUI tool that is designed to simplify the database conversion process tuning for the sqlways command-line tool. Works with the source database using the ODBC connection.
• SQLWays Studio – a GUI tool that is designed to simplify the database or application script conversion process tuning for the sqlways command-line tool. Works with one script at a time
• SQLWays Commander – a GUI tool that is designed to simplify the database or application scripts conversion process tuning for the sqlways command-line tool. Works with several scripts at a time.
• Sqlways.exe – a command line tool that can be in batch mode and can perform the automatic conversion of the database using the ODBC connection or the database and application code provided in scripts.
In this Demo I will show you common capabilities of SQLWays Wizard, SQLWays Studio and SQLWays Commander tools (mentioned in the list provided).
First, let’s start with SQLWays Wizard.
This is a tool that can connect to DB2 iSeries database using an ODBC connection. So to migrate from DB2 iSeries to Sybase ASE you need to provide an ODBC DSN for DB2 iSeries on a “Choose a source database page”. Also you need to specify a user and a password with the appropriate rights for making selection from system tables of DB2 iSeries.
On a “Choose a target database” page you need to choose a target database from the list of the supported databases. As you can see Sybase ASE database is specified here. You also need to provide other credentials for the Sybase ASE database for a support of definitions and data load using native utilities of this database
All the objects that SQLWays manages to extract from the DB2 iSeries are represented in a tree view on the “Specify Database Objects or Query” page. Here you can select all the objects required for the migration.
After that, you can specify different options for automated DB2 iSeries to Sybase ASE conversion. Here we can change settings for all selected objects or for separate groups of objects. We can set options that can control schema name conversion, reserved words conversion, data types conversion, identifier names conversion, object name and etc. (Also there are options that can help you to run the definitions and data migration as separate processes).
On the “Specify Export File Options” page you need to provide directory which serves as an intermediate repository for the whole migration process and stores all the automatically generated files like sql files with the converted definitions of the objects, text files with the data prepared to be loaded into the target database, bat or SH files with the commands for the native utilities to load the data.
The whole process of migration from DB2 iSeries to Sybase ASE is performed in two steps: export stage during which information is extracted from the source database and is converted, and import stage –which represents the download of information prepared to the target system. Each stage has its own reports with information on the progress of the migration.
For the export process there are sqlwayslog files that contain the information about the objects migrated from the source database, their number, the number of rows of data and the size of the data per each table extracted, the number of lines of code per each business logic object etc. At the end of the export log file there is a summary information per each object group and the information on the export status and issues if there are any.
Similar information but in more readable format is provided in the sqlways_report.html file.
As for the import stage SQLWays (Wizard) generates sqlways_imp.log file that contains information about objects that were loaded into the target database and whether there were any issues during the import process or no.
Data from the source database is mapped into csv files to be loaded into the target system.
Let’s check migration perfection. We call a procedure from the source database and now we call the same procedure from the target database to compare them. As you can see, the results are the same.
Now let’s run SQLWays Studio that can be used for sql scripts migration from DB2 iSeries to Sybase ASE. All you need to do to migrate scripts from DB2 iSeries to SAP HANA is to paste the script that you need to migrate in the left panel, choose the source and target directions and run the migration. In the right panel you can see the results of the migration.
And now let’s use SQLWays Commander that hepls to perform migration of files with sql scripts from DB2 iSeries to Sybase ASE. In order to migrate files with sql scripts we should choose the direction and run the migration. Once the migration the migration has been completed, in the right panel you can see a file with the same name. That is the converted file.
Then, SQLWays Commander allows to migrate several files at a time or the whole folder. To migrate the whole folder you need to select the folder, choose the migration direction and run the migration. Once the migration has been completed, in the left panel we can see this folder with converted scripts with the same name.
That’s all I wanted to tell you in this Demo. The information about the peculiarities of DB2 iSeries to SAP Hana migration and other tool that Ispirer Systems provides for database migration support will be described in our next Demos or can be found on our website. I hope this Demo was useful. Thank you!