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 |
|
ozgunnew
Starting Member
13 Posts |
 Posted - 2006-09-19 : 07:05:09
|
| Hi;Is there a possibility to start merge replication without syncronizing publisher and subscriber? I mean Can merge replication start when publisher and subscriber have different data? Thank you so much. |
|
|
Rishi Maini SQL2K5 Admin
Yak Posting Veteran
80 Posts |
Posted - 2006-09-19 : 14:45:36
|
| Yes create the Subscription with the option that Subscriber already has the schema and data.ThanksRishi Maini |
 |
|
|
ozgunnew
Starting Member
13 Posts |
Posted - 2006-09-19 : 15:42:49
|
| But i read that if publisher and subscriber have different data, it would cause problems. What i understand by choosing "Subscriber already has the schema and data.", is : we applied the snapshot file manually and subscriber and publisher are identical. Am i wrong? Thank you so much... |
|
|
|
Rishi Maini SQL2K5 Admin
Yak Posting Veteran
80 Posts |
Posted - 2006-09-21 : 03:57:28
|
| "Subscriber already has the schema and data" means that we do not need to apply the snapshot again as we are telling Replication that the Subscriber already has the data with it and is already in Sync with the Publisher. i.e. in recent past you have backed up the Publisher DB and restored it at the Subscriber. So in a way we are askign replication to just replicate the incremental changes rather than applying the whole snapshot over the wire. We generally use this option when there is a low Network bandwidth between Pub and Sub or the data is too large.Yes you are right choosing this option when the data is not consistent at Pub and Sub can land u in trouble. Imagine modifying a row at Publisher which does not exists at Subscriber. So yes you can "Can merge replication start when publisher and subscriber have different data" implement the Replication when the data is different at Pub and Sub using the manual Sync option but you need to make sure that no changes are made to that part of data that is not consistent at all the Replicas ThanksRishi Maini |
|
|
|
ozgunnew
Starting Member
13 Posts |
Posted - 2006-09-22 : 02:56:57
|
| I created replication a with the option that Subscriber already has the schema and data. And i tried it. There is no problem but a stange thing occurred which i do not expect according to your post. If data which does not exist at subscriber is modified in publisher it is replicated to subscriber. Is this normal? |
|
|
|
|
|
|
merge & initial syncronization