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 SP 6 » Tenant databases

Additional notes about adding tenant databases to the cloud

Version 10 and later databases can be added to the cloud.

Restrictions to tenant database names

Choose tenant file names and database names so that these names can be represented consistently in the character sets of all hosts in the cloud. Otherwise, if you move a database to a host that has a different character set, information could be lost. Also, the database name must be representable in the character set of the database itself. For example, if the database character set is CP1252, do not use characters from another character set in the database name.

Tenant database names:

  • Must not end in a well-known file name extension, such as .xml, .html, or .txt

  • Must not be longer than 128 characters in length

  • Can only contain a space ( ), pound sign (#), dash (-), percent sign (%), period (.), left parenthesis ((), right parenthesis ()), at sign (@), underscore (_), colon (:)

If possible, use 7-bit ASCII when naming tenant databases.

Databases that are configured to autostart and autostop

You can configure a database to autostart and autostop when it is added to the cloud.

Cloud Console versus the Cloud Database Add utility (dbcloudadd)

The Cloud Console is the recommended method for adding databases that are smaller than 100 MB and do not have dbspaces. If a database is larger than 100 MB or has dbspaces, then use the Cloud Add Database utility (dbcloudadd).

  • 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 17 database:

    • When a version 12 or earlier database is added to the cloud, it is upgraded to a version 17 database unless you specify that it be upgraded to version 12 or 16.

    • 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 or later 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.