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 » Support package upgrades » What's new in Support Package 3

 

Support for version 12 and version 16 databases and cloud servers

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. 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 the primary, mirror, and any scale-out database copies.

Databases can be upgraded when added to the cloud and anytime afterward. By default, databases are upgraded to version 16 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.

  • Cloud tasks and utilities affected by these enhancements   The following changes were made to support this feature.

    • Upgrading databases (UpgradeDatabase task)   You can now upgrade a database to the same software version as the cloud server that it is running on.

    • Load balancing (LoadBalanceDatabases task and Balancing database load)   When redistributing database copies running on overloaded cloud servers to cloud servers that have less activity, database copies are only moved to cloud servers that are of the same major and minor version.

    • Adding database copies (AddScaleOutDatabaseCopy task)   When a database copy is created, the database copy can only run on a cloud server that is of the same major and minor server version as the tenant database.

    • Moving databases and database copies (MoveDatabase task and MoveDatabaseCopy task)   When a database is moved from one cloud server to another, the version of the target cloud server must either match the major and minor version of the current database or be a later version. When a database copy is moved from one cloud server to another, the major and minor version of the cloud servers must match

    • Restoring databases from backups (RestoreBackupCopy task and RestoreBackup task)   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 other database copies of the tenant database. A database can only be restored to a cloud server whose version either matches or is later than the database major and minor version.

    • Add Cloud Database utility (dbcloudadd) enhancements to support version 16 databases and cloud servers   The following options were added to the Cloud Add Database utility (dbcloudadd):

      Option Description
      -upgrade_to_version [ 16 | 12

      This option is required to upgrade the database to version 12. Specify 12 to upgrade the database to major version 12 and add the database to a version 12 cloud server. Specify 16 to upgrade the database to major version 16 and add the database to a version 16 cloud server. The default is 16.

      The -server_list parameter can restrict the cloud server version that the database gets added to; however, the -upgrade_to_version parameter takes precedence.

      -system_procedure_as_definer [ on | off ]

      This option applies when upgrading to a version 16 database. It specifies whether the system procedures are to execute with the privileges of their owner (definer), or with the privileges of the invoker. By default, the system procedures retain the same invoker/definer setting as the original database.

 See also