A SQL Anywhere database running in the cloud is similar to a SQL Anywhere database running outside of the cloud.
However, there are a few features that are either not supported in the cloud or that have different behavior.
In most cases, tenant databases are added to the cloud, and then read-only copies of the tenant database can be created. However, it is possible to create a tenant database in the cloud by using a backup to restore a database. This new tenant database contains the same content as the database that the backup belongs to, but it has a unique name and runs on a different cloud server.
When a database is added as a tenant database to the cloud, it is upgraded.
Database mirroring can only be set up and managed by using cloud tasks and the Cloud Console.
When a database is added to the cloud, its login mode is modified to include the CloudAdmin login mode. This login mode is for internal use by the cloud.
See the documentation on connections to tenant databases.
To enforce strict tenant database isolation, the cloud server disables all secure features except backup. The secure feature key is set when the cloud is created.
You cannot apply a maintenance plan that is created in SQL Central to a tenant database running in the cloud.
The SQL Anywhere Backup utility (dbbackup) can create a backup copy of the tenant database that is stored outside the cloud. However, this backup contains cloud references.
When a database is running in the cloud, the following functions and system procedures return information for only the current tenant database. They do not show information about other tenant databases running on the same cloud server.
Request logging is not supported in the cloud. As a result, the following system procedures are not supported in the cloud:
When you run the CONNECT statement on a tenant database in the cloud, only syntax 2 is supported.
When using the following statements to specify the location of a transaction log, mirror log, or dbspace, you can only specify the name for the file. You cannot specify the directory location.
You cannot execute the following SQL statements on your tenant databases: