Demo presentation text:
This is the demonstration of the migration tools provided by Ispirer Systems for Oracle to Azure SQL Database migration.
In this presentation I will show you a brief demonstration of the migration from Oracle to Azure SQL Database with the help of Ispirer tools.
Before proceeding directly to the demo, I’d like to list the main 4 tools that we’re offering for an automated conversion:
• Ispirer Migration and Modernization Engine – a command line tool that can be run in batch mode and can perform the automatic conversion of a database or database and application code contained in scripts.
• Ispirer SQLWays Wizard – a GUI tool designed particularly for the database migration. It works with a source database using the ODBC connection.
• Ispirer Migration Studio – a GUI tool oriented specifically to the conversion of a separate application or database script. It works with one script at a time.
• Ispirer Migration Commander – a GUI tool designed for the conversion of multiple files containing application or database code. It works with several scripts at a time.
For the purposes of this demonstration, we have prepared two databases: an Oracle database and an empty Azure SQL Database where the migrated objects will be loaded.
Let’s start this trial migration with the first tool called Ispirer SQLWays Wizard. This is a fully featured tool developed exactly for a database migration.
When you start Ispirer SQLWays Wizard you see a Welcome page. Here you need to specify a license that you’ve got for this product and a project directory where a set of files required for the project is stored. Well, I’ve got it selected here, we can click next.
To migrate from Oracle to Azure SQL Database, you need to tune the ODBC DSN for Oracle and specify it on the “Choose a Source Database” page. Also you need to specify a user and a password with the appropriate rights for making selects from systems tables from Oracle.
On a “Choose a Target Database” page you need to choose the target database from the list of the supported databases. As you can see the MS SQL database is specified here. Also we need to provide other credentials like server name, database, user and a password for the Azure SQL Database for the support of definitions and data load using native utilities of this database.
All the objects that SQLWays manages to extract from Oracle it depicts 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 that help you to customize Oracle to SQL Database conversion, for example, the option that controls the schema name conversion, a reserved words conversion, data types conversion, identifier names conversion and etc.
On the “Specify Export File Options” page you need to provide the 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 code, TXT files with the data, BAT or SH files.
When it comes to an import process, here we should specify a BIN directory. A BIN directory is a path to native utilities. They will perform the import to Azure SQL Database.
In general, the whole migration process is performed in two steps: a conversion and an import.
In order to start the conversion, you just need to click Start on a “Migration Status” page. As soon as it’s over you can go to the “Import Status” page and perform the same. By the way, each of the steps has the separate logging information.
For the Export process, a sqlways.log file is provided. It contains the information about the objects read from the Oracle database, their number, number of rows of data, number of lines of code (LOC) per each business logics objects. At the end of the export log file, there is a summary information per each object type and the whole export process.
Similar information but in a much more readable format is provided in the sqlways_report.html file. Not only it contains a summary of the whole process, but there are also detailed statistics per each object extracted from the Oracle database.
As for the import process, SQLWays generates a sqlways_imp.log file regarding the import into the Azure SQL Database. It contains the information about the objects loaded and whether there were any issues during the import process or no.
Now, let me show you an example of the procedure in Oracle. As we can see, it contains some DML statements IF construction, RAISE APPLICATION ERROR, cursor usage, loop and exception handler.
Let’s call this procedure from our Oracle database. As a result it returned some data. Now I’m going to call the same procedure in Azure SQL Database. We can see that the data returned by the converted procedure is the same. So, the migrated procedure works correctly!
Now let’s continue the demonstration of Ispirer SQLWays Studio and Ispirer SQLWays Commander tools that were designed for database scripts and application scripts conversion.
In order to perform the conversion from Oracle to Azure SQL Database with the help of Ispirer Migration Studio all you need to do is to provide the conversion direction using the “Source” and “Target” options, insert the source Oracle code into the left pane of the tool and Run the conversion. As soon as the conversion is over, you can compare both source and target scripts in one tool side-by-side for your convenience.
As for Ispirer SQLWays Commander, the process is similar. In order to perform the conversion from Oracle to Azure you should specify the source and target from the list of supported databases, specify the files for the conversion and click Run. When you specify the directory for the conversion, you also need to provide the target folder, where the converted results will be placed. And you click OK.
As soon as the conversion is completed, by double-clicking the file in the source and in the file in the target pane you can review the conversion results side-by-side like in SQLWays Studio.
This is all the information dedicated to the migration from Oracle to Azure SQL database. If you’re interested in our prices or in other migration directions supported by Ispirer tools, feel free to contact us directly.
Thank you very much for your attention. Bye.