Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.
REMOTE and CONSOLIDATE permissions are very similar. Each database receiving messages from the current database must have an associated user ID on the current database that is granted one of REMOTE or CONSOLIDATE permissions. This user ID represents the receiving database in the current database.
The consolidated user is identified by a message system, identifying the method by which messages are sent to and received from the consolidated user. There can be only one consolidated user per remote database.
The remote user is identified by a message system, identifying the method by which messages are sent to and received from the consolidated user.
Databases directly below the current database on a SQL Remote hierarchy are granted REMOTE permissions, and the at most one database above the current database in the hierarchy is granted CONSOLIDATE permissions.
The GRANT REMOTE and GRANT CONSOLIDATE statements identify the message system and address to which replication messages must be sent.
CONSOLIDATE permissions must be granted even from read-only remote databases to the consolidated database, as receipt confirmations are sent back from the remote databases to the consolidated database. The GRANT CONSOLIDATE statement at remote SQL Anywhere databases is executed automatically by the database extraction utility.
Granting REMOTE permissions
Selecting a send frequency
Granting CONSOLIDATE permissions
Revoking REMOTE and CONSOLIDATE permissions