Teach you how to upgrade to SQL Anywhere 10 (1)

Upgrade SQL Anywhere

Attention:

Adaptive Server Anywhere has been renamed to SQL anywhere. In this article, we'll use SQL anywhere to refer to all versions of the product.

In version 10, the database format can only be upgraded by rebuilding the database, which includes unloading the old database and loading it into a new version 10 database. Data that is directly upgraded to version 9 or earlier can cause database startup to fail.

There are three ways to rebuild an existing database:

• Use the uninstall utility (Dbunload) with the-an (create a new database) or-ar (replace old database) option in version 10.

Attention:

The Unload utility (Dbunload) uses the same file name in the versions of SQL anywhere. So you have to make sure you use the correct version of the tool.

• Use the Unload Database Wizard provided in Sybase Central. You can choose to create a new database, or use a new database instead of old data, or unload the database into a file.

• Use the uninstall tool from the old database version and use the Reload.sql provided in version 10 to load the database. If you need to change the pattern, we recommend that you use this method. Once you have modified the schema, you can initialize a database and execute the rebuild script on it.

If you want to change the character set during unload and load (for example, to change the case-sensitive database to a case insensitive database), you may need more steps. For more information, refer to the SQL Anywhere documentation.

Compatible with existing software.

The SQL Anywhere 10 database server supports connections that are applied to version 6 or to an updated client. Version 5 or earlier clients cannot connect to the version 10 database server. When a version 9 or earlier client connects to a version 10 database server, the following attributes are not available:

· Kerberos logins.

• NChar data type embedded in SQL.

• Support for Unicode data that is promoted in ODBC, OLE DB, and ado.net (for example, nchar columns are described as WCHAR columns).

• Performance improvement for BLOB data, using Unicode applications in ODBC and all using OLE DB and

Ado. NET's application.

• Primarily for performance promotion in WAN environments (while also taking into account LAN environments).

Set up satmp for shared memory connections

The location of temporary files in version 10 and version 9, and earlier versions, takes a different search order. If you use version 9 or earlier clients to connect to a version 10 database server through shared memory, you must set up Satmp (version 10) and Astmp (version 9 and earlier) environment variables to specify the location of the temporary files. If you do not set these environment variables, attempts to share a shared memory connection will fail.

Managing legacy databases and servers in the current version of Sybase Central is as follows:

• You can connect and manage version 8 and newer databases running on version 8 or newer versions of servers.

• You can use Sybase to connect to a database that is running on version 5, 6, 7, 8, or 9 on a 8 or later version of the database server, and use the Unload Database Wizard to rebuild the database.

• We do not support version 6 or earlier databases running on version 7 or earlier database servers.