This is indeed a Service Broker question.
The steps necesary to deliver a notification remotely are:
- set up connectivity between ServerA and ServerB, see
- create a target service on ServerB that uses the event Notifications
- set up routes from database on ServerA to the target service and a route
from ServerB back to the Event Notifications service. see
http://msdn2.microsoft.com/en-us/library/ms166090(SQL.90).aspx for info
about routes. Note that for this case you must add the broker instances to
the route, because the event notification syntax require a broker instance
- set up security between the event notification service and the target
service, see http://msdn2.microsoft.com/en-us/library/ms166037.aspx and
The sequence of steps is explaind also here:
Using the Service Listing procedures can ease this task quite a bit, see
To troubleshoot your efforts, see this mini-guide
This posting is provided "AS IS" with no warranties, and confers no rights.
~ Remus Rusanu
SQL Service Broker
"SteveM" <[email protected]> wrote in message
> Little confused about Notification Services because all the examples
> I've found use one server.
> I would like to setup Event Notification so that Server level events
> such as Create Database on ServerA are sent to a centralized server
> (say ServerB) rather than collected on each server.
> If this is possible, what steps are required? I see the commands to
> create queue, service, and route, but my expectation is that these are
> on the destination server?
> Does anyone have an example of how to do this (if possible)