Teach you how to upgrade to SQL Anywhere10 (15)

Ultralite Application code upgrade tool

You can use the C + + API Migration Wizard to help you migrate C + + source code generated through Ulgen. Wizards help identify Embedded SQL that is no longer supported in the version 10 standard. If you are unable to complete the migration process, you can stop and save the modified SQL statement in a *.UAG file.

If this is the first time you use the wizard, the tables and statements will originate from the SQL Anywhere reference database. In subsequent iterations, you can use the saved *.uag file instead.

Porting the Ultralite C + + API in Sybase Central

1, please read carefully the important things in software upgrades.

2, make sure you have upgraded the SQL anywhere database and prepare it based on ultralite usage. If you need to upgrade your publication, be sure to do so before rebuilding the Ultralite database.

3, make sure that you have upgraded the Ultralite database. Otherwise, you will need to extract the Ultralite database from the SQL anywhere reference database.

4. Start Sybase in "Start" > "program" > "SQL Anywhere" > "Sybase".

5. Choose Tools > UltraLite > Transplant C + + applications to migrate the C/A + + application API.

6. On the source SQL statement page, select the statements and tables that are read.

If this is the first time you run the wizard, select and connect to the reference SQL anywhere database.

Otherwise, you can select the *.uag file that you created and modified before you opened the wizard to read the previous output file.

7, according to the code you choose, follow the instructions of the wizard and verify all SQL statements. Invalid statement will be in the statement name

There is a red X next to it.

To fix an invalid SQL statement:

A. Select an invalid statement.

B. Correct the statement within the text box.

C. Click to verify all SQL statements.

If the statement is validated, it appears at the end of the list and a green tick appears next to the statement name. You can click Cancel to save the changes to the. uag file and launch the wizard.

upgrading SQL Remote

If you upgrade an existing SQL Remote installation from version 6 or a newer version, you must first upgrade each database server and then upgrade its message agent (Dbremote). You can upgrade the message agent in any order.

• Upgrade the database. You must upgrade the database format by unloading and loading the database. You do not need to upgrade all databases at the same time.

• Software upgrades can be done on a per-point basis. The legacy message agent can exchange messages with the message agent of version 10.

• The message agent and database server can be upgraded separately. You can upgrade the database server before you upgrade the message agent. However, in view of the performance factors, we recommend that you upgrade the message agent at the same time.

• Upgrade the adaptive Server Enterprise consolidated database. The ASE Consolidated database is no longer supported by SQL Remote.

You need to use Mobilink if you want to sync with the ASE database.

Upgrade from SQL Remote installation of version 5

The installation of SQL remote includes a consolidated database and many remote databases with a message agent on each remote database.

At each site, the message agent is responsible for sending and receiving messages. The message is in the form of an SQL statement, and the database server is responsible for actually executing the SQL statement.

The following are requirements for upgrading SQL remote:

• Upgrade the database. Upgrade the database file format by unloading and loading.

• Software upgrades can be done on a per-point basis. The message agent for version 5 can exchange messages with the message agent of version 10, provided that the compression database option is set to-1. You do not have to upgrade at the same time.

• The message agent and database server can be upgraded separately. The message agent is an embedded SQL application. Therefore, the database server can be upgraded before the message agent is upgraded, as long as a compatible library is used. However, in view of the performance factors, we recommend that you upgrade the message agent at the same time.