Chapter 10. SQL Remote Administration
The
userid
isa user with CONNECT permissions on the current database.
Forexample, the following statement grants PUBLISH permissions to user
S_Beaulieu:
exec sp_publisher ’S_Beaulieu’
go
Thedatabase is set to have no publisher by executing the sp_publisher
procedurewith no argument:
exec sp_publisher
go
Noteson PUBLISH
permissions
♦Tosee the publisher user ID for an Adaptive Server Anywhere database
outsideSybase Central, use the CURRENT PUBLISHER special
constant. The following statement retrievesthe publisher user ID:
SELECT CURRENT PUBLISHER
♦Tosee the publisher user ID for an Adaptive Server Enterprise database,
usethe following statement:
SELECT name
FROM sysusers
WHERE uid = ( SELECT user_id
FROM sr_publisher )
go
♦IfPUBLISH permissions is granted to a user ID with GROUP
permissions,it is not inherited by members of the group.
♦PUBLISHpermissions carry no authority except to identify the publisher
inoutgoing messages.
♦Formessages sent from the current database to be received and processed
bya recipient, the publisher user ID must have REMOTE or
CONSOLIDATEpermissions on the receiving database.
♦Thepublisher user ID for a database cannot also have REMOTE or
CONSOLIDATEpermissions on that database. This would identify them
asboth the sender of outgoing messages and a recipient of such messages.
♦Changingthe user ID of a publisher at a remote database will cause
seriousproblems for any subscriptions that database is involved in,
includingloss of information. Youshould not change a remote database
publisheruser ID unless you are prepared to resynchronize the remote
userfrom scratch.
♦Changingthe user ID of a publisher at a consolidated database while a
SQLRemote setup is operating will cause serious problems, including
203