Argument Description
send_time
An optional string containing a time specification
withthe following meaning:
If
frequency
is SEND EVERY,specifies a length
oftime between messages.
If
frequency
is SEND AT,specifies a time of day
atwhich messages will be sent.
Ifno frequency is specified, the Message Agent sends
messages,and then stops.
Seealso “sp_revoke_remoteprocedure” on page 432
“GRANTREMOTE statement” on page 366
Description In a SQL Remote installation, each database receivingmessages from the
currentdatabase must be granted REMOTE permissions using the
sp_grant_remoteprocedure.
Theremote user is identified by a message system, identifying the method
bywhich messages are sent to and received from the consolidated user. The
address-namemust be a valid address for the message-system, enclosed in
singlequotes.
Thesp_grant_remote procedure is required for the remote database to
receivemessages, but does not by itself subscribe the remote user to any
data. Tosubscribe to data, a subscription must be created for the user ID to
oneof the publications in the current database.
Theoptional
frequency
argumentspecifies a frequency at which messages
aresent. The
send_time
argumentcontains a time that is a length of time
betweenmessages (for SEND EVERY) or a time of day at which messages
aresent (for SEND AT). With SEND AT,messages are sent once per day.
Ifno
frequency
argumentis supplied, the Message Agent processes
messages,and then stops. Inorder to run the Message Agent continuously,
youmust ensure that every user with REMOTE permission has a frequency
specified.
Itis anticipated that at many consolidated databases, the Message Agent will
berun continuously, so that all remote databases would have a
frequency
argumentspecified. Atypical setup may involve sending messages to laptop
usersdaily (SEND AT) and to remote servers every hour or two (SEND
EVERY).You should use as few different times as possible, for efficiency.
Example
394