Hi, If the database is set to Full recovery mode (SharePoint Default) then you have to make sure you've configured backups for your database and transaction log files. If you're already doing that then this article will help you determine a course of action to deal with a full transaction log:
http://msdn.microsoft.com/en-us/library/ms175495(v=sql.105).aspx Wes From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of Ajay Sent: Thursday, November 8, 2012 5:40 PM To: ozMOSS Subject: Re: Transaction Log is full Some more info The table it's trying to delete has 123788362 rows, maybe that's what causing it On Fri, Nov 9, 2012 at 11:15 AM, Ajay <akhanna...@gmail.com<mailto:akhanna...@gmail.com>> wrote: Hi Guys, I ran command to purge SharePoint audit log from database and it does not do anything and gives the following message The transaction log for database 'WSS_Content_Something' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases This database has been set to Full recovery mode Please advise,, Log_reuse_wait_desc query gives the following result NOTHING NOTHING NOTHING LOG_BACKUP LOG_BACKUP NOTHING NOTHING NOTHING LOG_BACKUP LOG_BACKUP NOTHING NOTHING NOTHING NOTHING LOG_BACKUP NOTHING LOG_BACKUP LOG_BACKUP NOTHING NOTHING NOTHING LOG_BACKUP LOG_BACKUP NOTHING LOG_BACKUP NOTHING NOTHING NOTHING CHECKPOINT LOG_BACKUP LOG_BACKUP NOTHING NOTHING NOTHING NOTHING NOTHING LOG_BACKUP LOG_BACKUP NOTHING NOTHING LOG_BACKUP NOTHING LOG_BACKUP NOTHING NOTHING NOTHING LOG_BACKUP NOTHING LOG_BACKUP NOTHING LOG_BACKUP LOG_BACKUP LOG_BACKUP LOG_BACKUP LOG_BACKUP NOTHING LOG_BACKUP LOG_BACKUP CHECKPOINT NOTHING LOG_BACKUP NOTHING LOG_BACKUP NOTHING NOTHING LOG_BACKUP LOG_BACKUP LOG_BACKUP NOTHING LOG_BACKUP NOTHING NOTHING NOTHING LOG_BACKUP
_______________________________________________ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
