Add databases to the cloud that are larger than 100 MB and/or have dbspaces.
The database must be version 10 or later.
The user ID and password for a database user:
For version 12 and earlier databases, the user must have DBA authority.
For version 17 and later databases, the user must have equivalent of the SYS_AUTH_DBA_ROLE compatibility role.
The user ID is stored in the cloud and is used later to connect to the database to perform administrative tasks. The password is discarded once the database has been added to the cloud.
If the database is encrypted, the encryption key for the database.
The cloud user must have the AddDatabase cloud privilege.
If a database is smaller than 100 MB and doesn't have dbspaces, then use the Cloud Console instead.
A database is always upgraded when it is added to the cloud. By default, the database is upgraded to a version 17 database. When upgrading to a version 17 database with the Cloud Add Database utility (dbcloudadd), the default is to retain the same invoker/definer setting as the original database.
C:\Program Files\SQL Anywhere on-demand 1.0\sa-win32-x86-22.214.171.12409-126.96.36.19909\Bin32
When specifying a name for the database in the cloud, ensure that it is a unique name among all tenant databases in the cloud and that it conforms to the tenant database name restrictions.
The database is uploaded, upgraded, and prepared to run in the cloud. The database is restarted in the cloud unless it is configured to autostart.
Run the following command to connect to the cloud and add a database named mydemo. In the cloud, this database is named Tenant1:
dbcloudadd -cc "HOST=myhost:2638;UID=admin;PWD=admin" -c "UID=DBA;PWD=sql;DBN=Tenant1" "c:\databases\mydemo.db"
To ensure the availability of your database, set up mirroring. Mirroring involves two cloud servers running the primary and mirror databases, and one cloud server running as the arbiter, which negotiates which database is the read-write copy.