Sybase Central includes a database migration tool. It uses ODBC to connect a Sybase db to a MySQL (or other) db.
To get the migration tool to work in Sybase Central it is necessary to update Central using the latest Engineering Bug Fix (EBF). The base version of Central crashes.
Using EBF to update 10.0.1 to build 3680, I can migrate some 30 tables having in all 700,000 plus records from MySQL to a new SQL Anwhere database created by command line in the Servoy/databases folder. Process time was less than five minutes.
However, whilst I can view the migrated tables in Sybase Central, version 10.0.1 build 3680 database appears to be incompatible with Servoy Developer Version 3.5.5-build 518 Java version 10.0-b19 (Windows XP). Servoy refuses to start up with the migrated database in the database folder, correctly specified in sybase config file. Yet I could start Servoy with the same database prior to migration (i.e. before build 3680 had touched it).
I have also attempted to create a new empty database using Sybase Central build 3680 rather than a command line within the Servoy/sybase_db folder. Servoy 3.5.5 also refuses to connect to this example.
I have logged this ussue as case 131588 with Servoy Support. Sybase UK are also aware of the issue.
In the interim it might be wise to steer clear of the migration tool, tantalising though it may be.
Has anyone else come across this issue, found a way to resolve it, or can suggest an alternative (and as easy) way to migrate from MySQL to SQL Anywhere 10?
Richard Hinder
Servoy Developer
Version 3.5.5-build 518
Java version 10.0-b19 (Windows XP)
Servoy support team have suggested “The problem can probably be fixed by copying dbcis10.dll from your Sybase Central installation to your Servoy SQL Anywhere directory.”
I have checked this out. The problem is not fixed by this move.
Although I have a specific issue to resolve concerning the migration of MySQL to SQL Anywhere, I can see in the background a wider issue. It is that there seems to be no smooth process for applying the lastest Engineering Bug Fixes advised by Sybase to a Servoy installation. Or am I wrong here?
Richard
Servoy Developer
Version 3.5.6-build 519
Java version 10.0-b19 (Windows XP)
It is that there seems to be no smooth process for applying the lastest Engineering Bug Fixes advised by Sybase to a Servoy installation. Or am I wrong here?
I think it depends on how you see this.
Servoy will always use the latest version that is stable and does the job as it is supposed to do it.
When bugfixes are crucial to Servoy or their customers it won’t take much time to convince them and it will be their issue to make sure it makes it to an update/upgrade.
When you want to be in control yourself there is nobody withholding you from using your own installation of Sybase like you already seem to do with MySQL.
That way it is not up to Servoy but up to you…
Many thanks for your thoughts Marcel. I appreciate that I might install Sybase myself. However, I have not looked into the issue of licenses. I have noticed that the servoy_sybase folder has a license file within it. I am not at all aware of how such a license might function in a separate installation of Sybase. The license file seems to be of the same build as the rest of the folder, and hence not the same as the build for the latest engineering bug fix.
Does anyone know about the issue of using Servoy licenses for Sybase in a separately installed (and more up to date) version of Sybase?