tag:blogger.com,1999:blog-20734372.post3373712589958684031..comments2023-08-26T12:18:21.101+02:00Comments on "Share"-Point: [MOSS/WSSv3] Audit Log and MergeContentDBSYorickhttp://www.blogger.com/profile/11902915833083267735noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-20734372.post-63125183263119834682010-09-07T23:17:30.577+02:002010-09-07T23:17:30.577+02:00Hi Tray,
When running the MergeContentDBS command...Hi Tray,<br /><br />When running the MergeContentDBS command, the audit table data is NOT transferred to the new database. So you can use the MergeContentDBS command to move the site collection to a new database and delete the old database. But keep in mind:<br />When the database still has some other site collections in it, there is no (supported) way to clean out the old audit data. The trimlogs command won't work anymore, as the site collection is not in that database anymore.Yorickhttps://www.blogger.com/profile/11902915833083267735noreply@blogger.comtag:blogger.com,1999:blog-20734372.post-40841434902424888202010-09-07T21:24:09.427+02:002010-09-07T21:24:09.427+02:00Hey Yorick. When you ran the mergecontentdb, was t...Hey Yorick. When you ran the mergecontentdb, was the audit table data transferred to the new database or not? The reason I ask is because we've run into an issue where our audit table has grown to several hundred GB's, and using the stsadm command to trim the table kills our SQL server. I'm trying to determine if I can just use mergecontentdb to move over to a new database, and hopefully the audit data won't get moved over with it.Trayhttps://www.blogger.com/profile/11770229856043454323noreply@blogger.com