Re: compensate_for_errors
- From: "Hilary Cotter" <hilary.cotter@xxxxxxxxx>
- Date: Fri, 12 May 2006 12:54:53 -0400
This controls what happens when there is a conflict. With compensate for
errors =true (default for SQL 2000), a conflict loser will have their data
replaced by teh conflict winner. With it false the conflict will merely be
logged, but the winning data will not replace the loosing data.
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Tigermikefl" <Tigermikefl@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9C16C143-962A-4856-92BF-F68D49884682@xxxxxxxxxxxxxxxx
Sorry for the battery of questions.
Are there any risks or complications from changing an article with
compensate_for_errors = false?
Does it force any reinitialization of subs?
Does it grow the msmerge_contents/tomb tables much?
I am guessing this will add some conflicts to manage. Is there a more
elegant, t-sql way to check and remove conflicts ie not one at a time.
Will the conflicts keep clearing out automatically with a new snapshot
generation?
SQL2K sp4 , merge pubs/dist with 50 msde sp4 anon pull subs.
Thanks in advance !!
--
Mike
If data falls in the woods and nobody is there to see it ....... ?
.
- Prev by Date: Re: Transformable v. regular subscriptions
- Next by Date: Re: Transformable v. regular subscriptions
- Previous by thread: Adding fields in Transactional Replication
- Next by thread: Re: compensate_for_errors
- Index(es):
Relevant Pages
|
