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.

 All Forums
 SQL Server 2000 Forums
 Import/Export (DTS) and Replication (2000)
 replication not working

Author  Topic 

maillisting
Starting Member

5 Posts

Posted - 2009-04-07 : 22:19:48
Hi all,
We have a merge replication between 2 servers. We insert records in subscriber but there is no record found in publisher. As it is a merge replication, the records should replicate to the publisher. Replication Monitor shows the replication is working normally. Below is my questions.

1. Beside, replication monitor, any log to show the detail about the replications?
2. If the data doesn't synchronize between 2 servers, how can I force MSSQL to check and do the replication again?
ango

RickD
Slow But Sure Yak Herding Master

3608 Posts

Posted - 2009-04-08 : 04:13:07
1.Yes, look at the conflict viewer. I think it is a right click on the publisher, but it is a long time since I have used SQL 2000.

2.The only way is to reinitialise the subscription, but you need to be careful as you will lose whatever is on the subscriber and not on the publisher. The only other thing to check is the merge update/insert/delete procedures as these sometimes get the wrong amount of parameters (seen it a few times before), but this should give you an error.
Go to Top of Page

maillisting
Starting Member

5 Posts

Posted - 2009-04-08 : 21:29:01
1. conflict table checked without records in it. Any other log/table can check deeply?

2. Data loss may happen if reinitialize the replication. Do you mean I need to manually merge update/insert/delete before reinitialized it? Since the table has million of records and manually merge is not quite possible. Any MSSQL process can help to check and do the merge?
Go to Top of Page

RickD
Slow But Sure Yak Herding Master

3608 Posts

Posted - 2009-04-09 : 03:51:08
1. Have you checked you ranges are still valid between you merged tables? This can also cause issues when the range is outside the check constraint. Have a look at DBCC CHECKIDENT()

2. Unfortunately yes, but you can do this by backing up and restoring your subscriber to a different database and writing a query to insert only those missing rows.
Go to Top of Page

maillisting
Starting Member

5 Posts

Posted - 2009-04-14 : 01:54:00
1. What do you mean of the range? How about if the table doesn't has an identity column in it?

2. It can be used for mismatch records but it is very difficult for the mismatch fields.
Go to Top of Page

sodeep
Master Smack Fu Yak Hacker

7174 Posts

Posted - 2009-04-14 : 22:50:06
Use validate subscribers to find mismatching data and use this to track any conflicts.

http://replicationanswers.com/Script_Merge_Conflicts.asp

Throw the job error to error log to investigate. Also you may want to see Pending tasks that are in distributor which has to go to publishers.
Go to Top of Page
   

- Advertisement -