Sybase DC38133-01-0902-01 manual Granting Consolidate permissions, Agent is run

Chapter 10. SQL Remote Administration

Setting the send frequency in Sybase Central

♦ Default setting (no SEND clause) If any user has no SEND AT or SEND EVERY clause, the Message Agent sends messages every time it is run, and then stops: it runs in batch mode.

In Sybase Central, you can specify the send frequency in the following ways:

♦When you make an existing user or group remote. For more information, see “Granting REMOTE permissions” on page 204 .

♦On the SQL Remote tab of the property sheet of a remote user or group. You can access the property sheet by right-clicking the remote user or group and choosing Properties from the popup menu.

Granting CONSOLIDATE permissions

	In the remote database, the publish and subscribe user IDs are inverted
	compared to the consolidated database. The subscriber (remote user) in the
	consolidated database becomes the publisher in the remote database. The
	publisher of the consolidated database becomes a subscriber to publications
	from the remote database, and is granted CONSOLIDATE permissions.
	At each remote database, the consolidated database must be granted
	CONSOLIDATE permissions. When you produce a remote database by
	running the database extraction utility, the GRANT CONSOLIDATE
	statement is executed automatically at the remote database.
Adaptive Server	The following Adaptive Server Anywhere statement grants CONSOLIDATE
Anywhere example	permissions to the hq_user user ID, using the VIM e-mail system:
	GRANT CONSOLIDATE TO hq_user
	TYPE vim
	ADDRESS ’hq_address’
	There is no SEND clause in this statement, so the default is used and
	messages will be sent to the consolidated database every time the Message
	Agent is run.
Adaptive Server	The following Adaptive Server Enterprise statement grants CONSOLIDATE
Enterprise example	permissions to user hq_user, using the file message link:
	exec sp_grant_consolidate ’hq_user’, ’file’, address
	go

Revoking REMOTE and CONSOLIDATE permissions

A user can be removed from a SQL Remote installation by revoking their REMOTE permissions. When you revoke remote permissions from a user or group, you revert that user or group to a normal user/group. You also automatically unsubscribe that user or group from all publications.

207