Removing Push Subscriptions when Publisher unavailable
Is there anyway to remove push subscriptions from SQL Server (2000) when the publisher is unavailable - we are extending a lients network and need to know "what if". We have tested and tried a second publisher - but we can not sign off this solution until to know how we will handle every possibility. Help appreciated we are running out of time.
ASKER
We have a main office and a branch office. at each location each workstation works on a local copy of a database and each evening all the workstations synchronise with the server in there rspective office. the branch office server then synchronises (merge replication) with the main office server. given our location (the pacific islands) there is the very real possibility that the server in the branch office will somehow cease functioning. if that happens then we will be left with 10 workstations subscribing to a now non-existant server in the branch office. the data is quite critical and time is a factor (it must all occur over night ready for the next days processing). should the branch (or main office) servers fail we need to be able to unsubscribe the workstations at that location and subscribe (push) to the server at the other location. how can we achieve this ?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks that has given us what we need to complete this documentation. Give me a second and I will accept it - even though you probably broke all the rules with that advertisement near the end. Will check out the site regardless of you cheeky sales pitch. Thanks heaps mate.
Ouch. You are correct. I was not aware of this rule. I was really not trying to prompote or advertise anything, just provide technical assistance using the best of my knowledge. I apologize for doing so.
1. You can always remove any subscription from a publication by manually writing into the system replication tables.
(e.g., unlist the subscriber server from sysservers, cleanup the subscriptions on that subscribers, etc.). One word of caution is that you must know where to clean and how (there are several objects you would have to clean, i.e., sysservers, syssubscriptions). [I assume here that you are talking about a transaction publication].
2. Are you using a local or remote distributor? You can always remove the subscriber from the distributor,
and not have to worry about the subscriber until a later time.
I am not really sure what you're asking, and for which purpose. We have done tons of work with replication.
If you can, please be more specific and re-post.
Hope this helps for now,
--------------------------
SQL Farms Solutions
www.sqlfarms.com