Strange Replication issue

We have 7 tables replicated continously using transactional replication between two SQL servers, which are part of a cluster setup. We get frequent issues of Data mismatch reported by users. BUT, Nothing shows up as an error in the SQL replication jobs.

We then do a "Re-Initialize" to re-sync the data and make it same. Again, some days later this issue recurs.

We are unable to pinpoint any issues. Anyone faced a similar scenario ? Thanks for your inputs.

Thanks,
Anand.K
akothand@indymacbank.com

"What would you attempt to do if you knew that you could never fail"
-Robert Schuller

1. Is it one way or using Immediate Updating Subscriber ?
2. Have you checked any Deadlock happening in your server
I faced this issue in Merger replication
Deadlock happens between the distributor process and application
process .The distributor is chosen as victim and some of the
records not gets replicated to other end.

And Ours is Transactional Replication. Had some bad experiences with Merge,so never adopting that anywhere now.

We have been analyzing perfmon reports for sometime now to solve a performance issue on the DB tier..We have an average of 70MB/sec reads, which is extremely high. But, our Application queries are in such a way. Apart from that, no real stand-out issues to answer the performance slowdown too.

And, am kind of hesitant to try Profiler so far as i think it might really add up to the server load.

Thanks,
Anand.K
akothand@indymacbank.com

"What would you attempt to do if you knew that you could never fail"
-Robert Schuller