June 14, 2017 at 6:56 am
We have set up a transactional replication but staff wants a warning to be sent from the subscriber side. I have done research and appears it only can be set up on the publisher side. Is this correct and if not, how can I set up warnings from the subscriber if replication had an error?
June 14, 2017 at 10:45 am
sdh96 - Wednesday, June 14, 2017 6:56 AMWe have set up a transactional replication but staff wants a warning to be sent from the subscriber side. I have done research and appears it only can be set up on the publisher side. Is this correct and if not, how can I set up warnings from the subscriber if replication had an error?
Are you referring to setting up replication alerts? If not, what specifically are you trying to set up? And why is there is need to send these or whatever warnings from a particular server? Not every role in the topology will necessarily know about issues you may be wanting to monitor so the request might not make sense.
Sue
June 14, 2017 at 10:54 am
Yes, I am trying to set up a replication alert if the transactional(scheduled every 5 min) records never make it over to the subscriber but have the alert come from the subscriber since I do not have access to the publisher/distributor server.
June 14, 2017 at 11:24 am
sdh96 - Wednesday, June 14, 2017 10:54 AMYes, I am trying to set up a replication alert if the transactional(scheduled every 5 min) records never make it over to the subscriber but have the alert come from the subscriber since I do not have access to the publisher/distributor server.
Those predefined alerts are installed on the distributor. Even without that, the subscriber won't know that records didn't make it over.
If someone mails me a package whenever xyz happens and I have no knowledge of if or when xyz happens then only the sender and/or the post office would know if there was a problem sending the package. Same type of thing where I would be the subscriber, the package sender is the publisher and the post office is the distributor. Not the best example but as close as I could think of for now.
The issue seems to be more one of being able to access the distributor or having someone with access that will work with you on that. If it's a third party system and you have access only to the replicated data on your end, talk to the vendor about what can be done to address your concerns. On the ones I've worked with like that, they can't give you access that exposes their other clients data and notices for clients typically won't happen based on whatever conditions. They often will notify you if things get very far behind though since it impacts there end - you would just need to contact and work with them.
Sue
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply