Data Replication with SQL Remote
PART 4. Reference
CHAPTER 18. Command Reference for Adaptive Server Enterprise
This procedure is used by the SQL Remote Message Agent, and should not be called directly, with a single exception described below. It manages rows in the sr_remoteuser table.
sp_remote operation, user_name [ , offset ] [ , confirm ]
Argument |
Description |
|---|---|
operation |
The name of an action. The only value that should be used by a user is reset; all others are for use by the Message Agent. |
user_name |
The name of the remote user being reset |
offset |
Not used |
confirm |
Not used |
This procedure is used by the SQL Remote Message Agent, and should not be called directly with the single exception of the reset call. It maintains the message tracking information in the sr_remoteuser table.
The following special case can be used directly, when creating a custom database extraction process:
sp_remote reset, remote_user
where remote_user is the remote user name.
This command starts all subscriptions for a remote user in a single transaction. It sets the log_sent and confirm_sent values in sr_remoteuser table to the current position in the transaction log. It also sets the created and started values in sr_subscription to the current position in the transaction log for all subscriptions for this remote user. The procedure does not do a commit. You must do an explicit commit after this call.
In order to write an extraction process that is safe on a live database, the data must be extracted at isolation level 3 in the same transaction as the subscriptions are started.