[Top] [All Lists]

Re: Event Notification using multiple SQL Servers (source / destination)

Subject: Re: Event Notification using multiple SQL Servers source / destination
From: "Remus Rusanu [MSFT]"
Date: Thu, 23 Feb 2006 09:43:48 -0800
Newsgroups: microsoft.public.sqlserver.notificationsvcs, microsoft.public.sqlserver.servicebroker
Hello Steve,

This is indeed a Service Broker question.

The steps necesary to deliver a notification remotely are:
- set up connectivity between ServerA and ServerB, see , and
- 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 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 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,SQL.90).aspx

"SteveM" <[email protected]> wrote in message
news:[email protected]
> 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)

<Prev in Thread] Current Thread [Next in Thread>