There are some considerations when upgrading a database.
Notes about upgrading a database when adding it to the cloud A database is always upgraded when it is added to the cloud. By default, the database is upgraded to a version 16 database:
When a version 16 database is added to the cloud, it is upgraded to a version 16 database.
When a version 12 or earlier database is added to the cloud, it is upgraded to a version 16 database unless you specify that it be upgraded to a version 12.
The upgraded database is added to a cloud server that is of the same major and minor version. Once the database is in the cloud, it can be moved to a cloud server that has a higher major and minor version afterward.
For example, if you want a version 12 database to run on a version 16 cloud server, then add the database to the cloud and specify that the database be upgraded to a version 12 database and specify the version 12 cloud server to use. Once the database is in the cloud, move the database to a version 16 cloud server.
Changes for system procedures that perform privileged operations Whenever a database is upgraded to a version 16 database, you must specify whether system procedures that perform privileged operations execute with the privileges of their owner (definer) or with the privileges of the invoker.
When adding a database by using Cloud Console, these system procedures are by default set to execute with the privileges of the invoker. When using the Cloud Add Database utility (dbcloudadd), the system procedures by default retain the same invoker/definer setting as the original database.
When upgrading a database that already exists in the cloud, the default is to retain the invoker/definer setting of the database being upgraded.
Discuss this page in DocCommentXchange.
|Copyright © 2014, SAP AG or an SAP affiliate company - SAP SQL Anywhere, on-demand edition 1.0|