onflit_MyPubName_MyArticle ; MSmerge_genhistory

Hi,
1 ) is there a way to drop the conlict table ? (named
?onflit_Pubname_ArticleName)
where ? can a;b;c etc...
Why aren't they erased when the conflict is solved ?
2) Why do i have to execute this
delete
from MSmerge_genhistory
where generation not in (select generation from msmerge_contents)
and generation not in (select generation from msmerge_tombstone)
dbcc dbreindex ('msmerge_genhistory')
Why SQL does not do it itself ?
SQL 2K SP2
Thanks
1) use do a drop aconflict_... however, I would not do this as you might
inadvertently drop a table which is in use.
2) Replication metadata is purged by default every two weeks. This should
take care of your first statement. If msmerge_genhistory does get too
fragmented you might want to reindex it. I can't comment on why Microsoft
decided not to do this automatically, but I am sure they had a good reason.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Pierre Marie" <PierreMarie@.discussions.microsoft.com> wrote in message
news:DF63D725-F345-4FA2-9F4A-C70D9D9ED3ED@.microsoft.com...
> Hi,
> 1 ) is there a way to drop the conlict table ? (named
> ?onflit_Pubname_ArticleName)
> where ? can a;b;c etc...
> Why aren't they erased when the conflict is solved ?
>
> 2) Why do i have to execute this
> delete
> from MSmerge_genhistory
> where generation not in (select generation from msmerge_contents)
> and generation not in (select generation from msmerge_tombstone)
> dbcc dbreindex ('msmerge_genhistory')
> Why SQL does not do it itself ?
> SQL 2K SP2
>
> Thanks
>