sp_mergemetadataretentioncleanup
-
Tuesday, November 13, 2012 5:33 PM
Can someone explain how this stored procedure works? I have a republishing server with a lot of msmerge_genhistory records. This is causing the initial snapshot to take a long time and was actually causing an error to initialize from the snapshot until i increased the query timeout. If I do a count of the records in msmerge_genhistory and group by subscriber server and left join to sysmergesubscriptions on subscriber number I see that most of the records in msmerge_genhistory have a null subscriber server and a null last sync date. I'm not sure but wouldn't the cleanup stored proc work off the last sync date in sysmergesubscriptions. And for this metadata in msmerge_genhistory since most of the records have a null last sync date shouldn't that be cleaned up. It would be nice to get rid of these records if possible so initializing from the snapshot would perform much better.
All Replies
-
Tuesday, November 13, 2012 6:10 PMModerator the metadata cleanup looks at coldat on msmergegen_history. It will purge rows from gen_history, msmerge_contents, and msmerge_tombstone as they become older than the retention data +1. There are some exceptions.
looking for a book on SQL Server 2008 Administration? http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search? http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941
- Marked As Answer by nighttrain79 Tuesday, November 13, 2012 9:55 PM
.png)
