Conflict table cleanup interval

What replication parameter sets the interval in which data in the conflict tables is deleted in SQL Server 2000 SP4?Apparently when the snapshots are generated the conflict tables are cleaned out as part of the process. This was causing my conflicts to disappear each night when the snapshot agent ran.|||

Rerunning snapshot should not be cleaning the tables.

@.conflict_retention governs how long the data will be kept in these tables before purging.

|||If I have data in the conflict tables and then execute the snapshot SQL Agent job the conflict tables are cleaned out. I have the @.conflict_retention value set to 90 days.
The publication is a filtered merge publication.|||

Sorry I missed your earlier comment that this was SQL Server 2000.

This is a known issue in SQL Server 2000 and has been fixed in SQL Server 2005.

Conflict table cleanup

Hello All -
Is there a process that automatically cleans the conflict tables?
I have a merge publication with publisher & distributer running on same
machine. This is SQL 2K and W2K host. The clients are push subscription.
I viewed several conflicts last week ( Friday) and postponed resolving them.
There were about 300 conflicts and I didn't view them all.
Today when I went to view them, EM told me that 'no conflicts table'.
Is there some automatic clean of the conflict tables?
Do conflicts get purged when re-initializing all client?
Thanks,
bruce
Yes we do cleanup the rows when the subscription is re-initialized, also
the conflict rows are deleted when we manually resolve it from the conflict
resolver.
thanks
gopal
|||Bruce,
This is not a cleanup, but a wipe out! Your problem could be related to the
fact that the Snapshot Agent may be running automatically.
Everytime this agent runs the conflict tables are dropped and recreated
(they say this is by design), therefore you will lose any conflicts that
were there before.
Raj Moloye

Conflict data automatic cleanup

What replication parameter sets the interval in which data in the
conflict tables is deleted in SQL Server 2000 SP4?
The data in my conflict tables appears to be deleted every night.
From BOL: "The Merge Agent deletes data from the conflict table if it is
older than the conflict retention period for the publication, which is
specified using the @.conflict_retention parameter of sp_addmergepublication
(the default is 14 days)."
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||the default is every 14 days. You set it with @.conflict_retention parameter
of sp_addmergepublication
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
"zebra1024" <jcmackenzie@.gmail.com> wrote in message
news:1163168845.703224.81300@.f16g2000cwb.googlegro ups.com...
> What replication parameter sets the interval in which data in the
> conflict tables is deleted in SQL Server 2000 SP4?
> The data in my conflict tables appears to be deleted every night.
>
|||I thought that was the parameter but my conflict tables seem to be
cleaned out each night even though this parameter is set to 14. Does
generating the snapshots clean out these tables also?
Paul Ibison wrote:
> From BOL: "The Merge Agent deletes data from the conflict table if it is
> older than the conflict retention period for the publication, which is
> specified using the @.conflict_retention parameter of sp_addmergepublication
> (the default is 14 days)."
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||I just tested this and apparently generating the snapshots does clean
out the conflict tables.
zebra1024 wrote:[vbcol=seagreen]
> I thought that was the parameter but my conflict tables seem to be
> cleaned out each night even though this parameter is set to 14. Does
> generating the snapshots clean out these tables also?
>
> Paul Ibison wrote:
|||Very interesting - thanks for the update. I'll request a BOL update for
this, as it is not mentioned in the right place (if at all).
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .