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 - 2001-12-24 : 09:52:01
|
| Merith writes "Hi SQLTeam,Phew, am i glad to stumble onto yr site! Fyi, i've been posting this problem of mine everywhere (well, not exactly... just a few) and not exactly getting lots of suggestions. Some suggested i should run SP2 or higher, but b4 i do, here's what's been giving me sleepless nights..... i think i have a serious problem. i have > 20,000 rows (as of this minute and counting ....) with the following conflict on a table (generated by merge replication over a period of close to 4 weeks) :'The row was updated at 'SubscriberServer3.DatabaseA' but could not be updated 'at 'PublicationServer1.DatabaseA'. Metadata mismatch'i have 20 remote subscribers & 1 publisher. The above message originates from practically everywhere.Besides dropping(not practical at the moment) & recreating replication to get rid of them, what else can i do to resolve this problem (and maintain data correctness)?? Do i have to resolve this problem row by row?? Where do i start? i'm at my wit's end. Please help!!Thanx in advance,Merithp/s: By the way, u people have a real neat site here." |
|
|
|
|
|
SQL 7.0 Merge Replication Conflict