Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
SQLServerDBA_Dan
Aged Yak Warrior
752 Posts |
 Posted - 2001-12-02 : 19:30:43
|
I feel I know snapshot and transactional quite well but merge is a bit new to me. I'm hoping someone can answer this quick question: When you setup the publisher and use a push or a pull subscription, do the changes on the subscriber get applied to the publisher? If this is the case, is there anything additional to setup besides the push or pull?If there is a post that is already about this please post a link to it.  DanielSQL Server DBA |
|
|
PiecesOfEight
Posting Yak Master
200 Posts |
Posted - 2001-12-02 : 20:20:22
|
| There are a lot of things you can set up with merge, but the basic setup allows you to make changes at the Publisher and Subscriber(s) and the changes flow to all servers. If there are conflicts (e.g. the Subscriber updates a column in a row to 10 and the Publisher updates the same column to 15), these will be handled either by using the defaults or by using custom resolvers. |
 |
|
|
SQLServerDBA_Dan
Aged Yak Warrior
752 Posts |
Posted - 2001-12-03 : 01:32:47
|
quote:
There are a lot of things you can set up with merge, but the basic setup allows you to make changes at the Publisher and Subscriber(s) and the changes flow to all servers. If there are conflicts (e.g. the Subscriber updates a column in a row to 10 and the Publisher updates the same column to 15), these will be handled either by using the defaults or by using custom resolvers.
Cool thanks.So just by making a publication and having a subscriber setup it will apply the changes, either made on the published server or subscribing server, to all servers. Is that right?Regards,DanielSQL Server DBA |
|
|
|
Tim
Starting Member
392 Posts |
Posted - 2001-12-03 : 08:36:39
|
Hey Dan,If you are going to merge, use SQL2k... SQL 7 sucks in comparison for merge replication... too many restrictions.Here are my setup steps if it helps...I have distributor, publisher and publication setup with appropriate entries in the PAL.subscribers (SQL Servers) have to be configured.run the snapshot job for the publication, and then subscriptions can be intialised (push or pull)After that changes at any system are eventually propagated to all systems apart from conflicts.Here is one to watch out for that isn't handled by default.Two subs have same record from a parent table with no children.Sub A adds a child record, sub B deletes the parent.Now when the subscribers synchronise they will crash if you have RI constraints, because either adding an orphan or creating one when the 2nd change is done at the publisher. You can use NOT FOR REPLICATION on the RI constraints to avoid the crash but you still have to clean up the orphaned records at pub/subs (unless you don't mind crappy data).good luck...-------------------------------Visit nr's cursor wonderland  |
|
|
|
SQLServerDBA_Dan
Aged Yak Warrior
752 Posts |
Posted - 2001-12-03 : 09:57:26
|
quote:
Here is one to watch out for that isn't handled by default.Two subs have same record from a parent table with no children.Sub A adds a child record, sub B deletes the parent.Now when the subscribers synchronise they will crash if you have RI constraints, because either adding an orphan or creating one when the 2nd change is done at the publisher. You can use NOT FOR REPLICATION on the RI constraints to avoid the crash but you still have to clean up the orphaned records at pub/subs (unless you don't mind crappy data).good luck...
Thanks.  |
|
|
|
|
|
|
|
|
a simple merge replication question