Chapter 5. A Tutorialfor Adaptive Server Enterprise Users
Tocreate the publisher
1. Add a login called hq_user, with hq as the default database and with
systemadministrator access:
exec sp_addlogin hq_user, hq_pwd, hq
go
exec sp_role ’grant’, sa_role, hq_user
go
2. Add the login name as a user to the HQ database:
use hq
go
exec sp_adduser hq_user
go
3. Make this user the publisher of the HQ database:
exec sp_publisher hq_user
go
Adda remote user Eachremote database is identified in the consolidated database by a user ID
withREMOTE permissions. Whetherthe remote database is a single-user
serveror a database server with many users, it needs a single user ID to
representit to the consolidated database.
Ina mobile workgroup setting, remote users may already be users of the
consolidateddatabase, and so no new users would need to be added;
althoughthey would need to be set as remote users.
Whena remote user is added to a database, the message system they use and
theiraddress under that message system need to be stored along with their
databaseuser ID.
Tocreate the subscriber
1. If you do not have a login name that you can use for the remote user, add
alogin:
exec sp_addlogin field_user, field_pwd, hq
go
2. Add a user to the hq database:
exec sp_adduser field_user
go
3. Grant the user remote permissions. Executethe sp_grant_remote stored
procedure,using field_user as the user name, file as the message type,
andthe appropriate directory as the address:
61