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

How do tenant databases differ from non-cloud databases?

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.

  • Database creation in the cloud

    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.

  • Databases are upgraded when added to the cloud

    When a database is added as a tenant database to the cloud, it is upgraded.

  • Database mirroring system must be done within the cloud

    Database mirroring can only be set up and managed by using cloud tasks and the Cloud Console.

  • New login mode value for databases in the cloud

    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.

  • Connection parameter requirements and restrictions

    See the documentation on connections to tenant databases.

  • Secure feature key

    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.

  • Maintenance plans created in SQL Central are not supported in the cloud

    You cannot apply a maintenance plan that is created in SQL Central to a tenant database running in the cloud.

  • Backup utility (dbbackup) can back up databases outside 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.

  • Limitations on the results from system procedures and functions when run on a database in the cloud

    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.

    • Functions
      • CONNECTION_EXTENDED_PROPERTY function [String]
      • CONNECTION_PROPERTY function [System]
      • DB_EXTENDED_PROPERTY function [System]
      • DB_ID function [System]
      • DB_NAME function [System]
      • DB_PROPERTY function [System]
      • NEXT_CONNECTION function [System]
      • NEXT_DATABASE function [System]
    • System procedures
      • sa_conn_activity system procedure
      • sa_conn_compression_info system procedure
      • sa_conn_info system procedure
      • sa_conn_list system procedure
      • sa_conn_options system procedure
      • sa_conn_properties system procedure
      • sa_db_info system procedure
      • sa_db_list system procedure
      • sa_db_properties system procedure

      Request logging is not supported in the cloud. As a result, the following system procedures are not supported in the cloud:

      • sa_get_request_profile
      • sa_get_request_times
  • SQL statements that have limited functionality for tenant databases

    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.

    • CREATE DBSPACE statement
    • ALTER DATABASE statement
    • ALTER DBSPACE statement
  • SQL statements that are not supported in tenant databases

    You cannot execute the following SQL statements on your tenant databases:

    • ALTER MIRROR SERVER statement
    • CREATE DATABASE statement
    • CREATE MIRROR SERVER statement
    • DROP MIRROR SERVER statement
    • SET MIRROR OPTION statement
    • START DATABASE statement
    • STOP DATABASE statement
    • STOP SERVER statement