lossof information. Youshould not change the consolidated database
publisheruser ID unless you are prepared to close down the SQL Remote
setupand resynchronize all remote users.
Granting and revoking REMOTEand CONSOLIDATE permissions
REMOTEand CONSOLIDATE permissions are very similar. Each database
receivingmessages from the current database must have an associated user
IDon the current database that is granted one of REMOTE or
CONSOLIDATEpermissions. This user ID represents the receiving
databasein the current database.
Databasesdirectly below the current database on a SQL Remote hierarchy
aregranted REMOTE permissions, and the at most one database above the
currentdatabase in the hierarchy is granted CONSOLIDATE permissions.
SettingREMOTE and
CONSOLIDATE
permissions
ForAdaptive Server Anywhere, the GRANT REMOTE and GRANT
CONSOLIDATEstatements identify the message system and address to
whichreplication messages must be sent.
ForAdaptive Server Enterprise, the sp_grant_remote procedure sets
REMOTEpermissions, and the sp_grant_consolidate procedure sets
CONSOLIDATEpermissions.
CONSOLIDATEpermissions must be granted even from read-only remote
databasesto the consolidated database, as receipt confirmations are sent
backfrom the remote databases to the consolidated database. The GRANT
CONSOLIDATEstatement at remote Adaptive Server Anywhere databases
isexecuted automatically by the database extraction utility.
Granting REMOTEpermissions
Eachremote database must be represented by a single user ID in the
consolidateddatabase. This user ID must be granted REMOTEpermissions
toidentify their user ID and address as a subscriber to publications.
GrantingREMOTE permissions accomplishes several tasks:
Itidentifies a user ID as a remote user.
Itspecifies a message type to use for exchanging messages with this user
ID.
Itprovides an address to where messages are to be sent.
Itindicates how often messages should be sent to the remote user.
GrantingREMOTE permissions is also referred to as adding a remote user
tothe database.
204