User's Manual

For any database in a SQL Remote replication setup, there are three
permissions that may be granted to identify databases on the hierarchy:
PUBLISH permission Identifies the current database in all outgoing
messages
REMOTE permission Identifies each database receiving messages from
the current database that is below it on the hierarchy
CONSOLIDATE permission Identifies a database receiving messages
from the current database that is directly above it on the hierarchy.
Permissions can only be granted by a user with DBA authority. To carry out
these examples you should connect from Sybase Central to the hq database
as user ID DBA, with password SQL.
Add a database
publisher user ID
Any database, consolidated or remote, that distributes changes to other
databases in the replication system is a publisher database. Each database in
the replication system is identified by a single user ID. You set that ID for
your database by adding a publisher to the database. This section describes
setting permissions for the consolidated hq database.
First create a user ID named hq_user, who will be the publisher user ID.
To create a new user as the publisher
1. Select the Users & Groups folder.
2. From the File menu, choose New User.
The User Creation wizard appears.
3. Enter the name hq_user, with password hq_pwd, and click Finish.
4. Right-click the hq_user icon and choose Change to Publisher from the
popup menu.
A database can have only one publisher. You can find out who the
publisher is at any time by opening the Users & Groups folder.
Add a remote user Each remote database is identified in the consolidated database by a user ID
with REMOTE permissions. Whether the remote database is a personal
database server or a network server with many users, it needs a single user
ID to represent it to the consolidated database.
In a mobile workgroup setting, remote users may already be users of the
consolidated database, and so no new users would need to be added;
although they would need to be set as remote users.
When a remote user is added to a database, the message system they use and
their address under that message system need to be stored along with their
database user ID.
36