Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.

SAP SQL Anywhere, on-demand edition 1.0 » SAP SQL Anywhere, on-demand edition » Cloud administration

 

Multiple software versions of cloud servers and databases

A cloud can support multiple versions of cloud server and database software.

The following rules apply:

  1. The major and minor version of the database must be equal to or earlier than the major and minor version of the cloud server. For example a version 12 database can run on a version 12 cloud server or on a version 16 cloud server. And a version 16 database can run on a version 16 cloud server, but a version 16 database cannot run on a version 12 cloud server.

  2. When a tenant database is involved in a mirroring or read-only scale-out system, then all of its database copies must run on cloud servers that are of the same major and minor version. In a mirroring system, the arbiter server must also be of the same major and minor version as primary, mirror, and any scale-out database copies.

When a database is moved from one cloud server to another, the target cloud server must either match the major and minor version of the current database or be a newer version. A database copy can only be moved to a cloud server that has the same major and minor version as the cloud server of the tenant database. These rules also apply when load balancing databases.

When a database is restored, it must be added to a cloud server that either matches the major and minor version of the database or be a newer version. A database copy can only be restored to a cloud server that has the same major and minor version as the cloud server of the tenant database.

Databases can be upgraded when added to the cloud and anytime afterward. By default, databases are upgraded to version 16 and when they are added to the cloud. Whenever a database is upgraded to a version 16 database, you must specify whether the system procedures execute with the privileges of their owner (definer) or with the privileges of the invoker. When adding a database or upgrading a database, the system procedures by default retain the same invoker/definer setting as the original database.

 See also