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 |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2006-08-23 : 09:41:31
|
| Zubin writes "Hi,I am using MS SQL Server 2000 with Service Pack 2.0. I am using transactional replication across two databases on two different servers using optical fibre for connectivity. Some orders are being replicated from the publisher to the subscriber. Everything runs smoothly but once in a while a particular column when updated does not get replicated to the subscriber. I am unable to understand this as it happens say about once in every 500 orders. Otherwise all fields are replicated during updates.Can you help?Thanks.Zubin." |
|
|
Rishi Maini SQL2K5 Admin
Yak Posting Veteran
80 Posts |
Posted - 2006-08-27 : 10:49:46
|
| First of all I would recommend to upgrade to Service Pack 4. If there is a convergence issue in Transactional Replication you need to figure out if the Data is being replicated to the Distributor Database or not. The flow of Data in Transactional Replication is as follows:- A.) Log Reader picks the changes (for replicated artciles) from the log file of the Published Database and pushes it to the Distribution Database.b.) At the Distribution Database Data is stored is "msrepl_transactions" and "msrepl_commands" Table.c.) Distribution Agent then picks the Data from these two Tables and Pushes it to the Subscriber.We do not know if in your case the problem is between "Publisher-Distributor" or from "Distributor-Subscriber". You need a indepth knowledge of Replication to troubleshoot Non-Convergence issues in Replication.My recommendations:- a.) Apply Service Pack 4 ASAP to skip any known issues with Transcational Replication while ur on SP2.b.) Contact the Microsoft Support to troubleshoot further.ThanksRishi Maini |
 |
|
|
|
|
|
Transactional Replication skips an updated column randomly.