Demo presentation text:
On behalf of Ispirer Systems, I would like to welcome you to the demonstration of the migration tools provided by our company.
This presentation will be devoted to Sybase Adaptive Server Enterprise to Microsoft SQL Server migration.
In this video, you will see how easy the migration from Sybase to SQL Server can be performed by Ispirer Toolkit.
To start with, we'll give you just a one-minute description of the Ispirer Migration and Modernization Toolkit 2015,
and then we’ll go on to the database migration from Sybase to SQL Server.
Basically, there are four tools called
• Ispirer Migration and Modernization Engine – it can be run in batch mode, and performs the automatic conversion of the database or the database and application code contained in scripts.
• Ispirer SQLWays Wizard is a GUI tool designed particularly for the database migration. It works with the source database using the ODBC connection.
• Ispirer Migration Studio is a GUI tool oriented specifically to the conversion of a separate application or database script. Works with one script at the same time.
• Ispirer Migration Commander is a GUI tool designed for the conversion of multiple files containing application or database code. The difference is that it can work with several scripts simultaneously.
Let’s now begin the demonstration of Sybase to SQL Server database migration.
For the purposes of this demo, we have prepared two databases: Sybase database, which contains object for migration and an empty SQL Server database. The objects will be migrates from Sybase into this very database.
Let’s convert this database with the help of the Ispirer Toolkit.
So we start with the Ispirer SQLWays Wizard – we can see it on the screen.
This tool can connect to the Sybase database through the ODBC connection only. So, to migrate from Sybase to SQL Server, we need to tune the ODBC DSN for Sybase.
And for the target SQL Server database it creates the native tool commands.
On the SQLWays Wizard Welcome page we enter the license information for this product. And also we specify a project directory that contains the objects for the conversion and the files with information about conversion options.
Well, we’ve selected it, and we can click next.
On a «Choose a source database» page we need to specify a user or system DSN name for the ODBC connection for Sybase. Then- the user name with the appropriate rights to work with the system tables in Sybase and a password.
We go next and
On a «Choose a target database» page we choose SQL Server from the list.
We also need to specify server name, database, user name and a password that we are going to use for loading the objects to SQL Server.
On a «Specify database objects» page we can see all the objects of the source database specified in a tree view. Here we can select all the objects required for the migration. We see the tree view of the selected objects in the right pane.
On a «Specify DDL and data options» page we can specify different options that help us to customize the conversion,
like option that controls the schema name conversion, reserved words conversion, data types conversion, and etc
On a «Specify an export file options» page we identify the «Export directory» which will serve as an intermediate repository for all the files which will be generated during the conversion.
Well, the migration process is performed in two stages. And for each of them logging information is provided.
We have a «View export» page and SQLWays log file that depicts export process.
It contains information about the objects read from the Sybase database, their number, number of rows of data and the size of data per each table extracted, number of lines of code (LOC) per each type of business logics objects.
And at the end of the export log file we can see summary information per each object type and for the whole database export process.
The same information about the export process but in a more structured and readable format can be reviewed in SQLWays_report.html file.
There is an object summary page, volume of data for tables, lines of code for business logic objects and summary information. We can review the detailed statistics for each object type extracted from Sybase database.
If we are talking about the import process, SQLWays generates a sqlways_imp.log file (import log file) that represents the import into the SQL Server system. This file shows the objects loaded and import process issues, if any.
Now, lets look for example at a procedure in Sybase.
As we can see, the procedure contains some representative statements like if…then construction, DML statements, raise exception statement, and dynamic SQL.
Let’s call this procedure from our Sybase database. We can see that it returned some data.
Now lets execute the same procedure in SQL Server and we can see that the data returned by the converted procedure is the same. So the procedure migrated works correctly!
Now let’s move on to the Ispirer Migration Commander and Ispirer Migration Studio tools which are designed to perform scripts conversion.
Ispirer Migration Studio works with one script at the same time.
To accomplish the conversion, all you need is to specify the source and the target, insert a fragment of the Sybase code into the left pane. And click run.
The results of the conversion can be compared in both left and right panes side-by-side for your convenience.
Let's look now at the Ispirer Migration Commander. The main principle of work is the same - it converts scripts, but it allows converting multiple scripts simultaneously.
In order to perform the conversion we just need to specify the source and target,
choose the files for conversion and click run.
!We can specify a file, multiple files, or the entire directory for the conversion.
When we specify the directory for the conversion we also need to provide the target folder, where converted results will be placed. And click Ok.
By double-clicking the file in the source and in the target window we can review the conversion results side-by-side.
Well, that concludes my presentation about the automatic database migration from Sybase Adaptive Server Enterprise to Microsoft SQL Server utilizing Ispirer tools.
That was an overview of the tools and their supported features. Now I'd like to invite any questions you may have about the conversion performed by Ispirer Toolkit. Please just contact Ispirer, and get our free assistance and expertise support.
I’d like to thank you for your attention and interest. Bye.