April 12, 2011 at 7:34 am
Executing the query "ALTER INDEX [CollectionMembers_SMSID_idx] ON [dbo].[CollectionMembers] REBUILD WITH ( PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, SORT_IN_TEMPDB = ON, ONLINE = OFF )
" failed with the following error: "Transaction (Process ID 63) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
Executing the query "ALTER INDEX [AuditData_OnSiteOccurredEvent] ON [dbo].[AuditData] REBUILD WITH ( PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, SORT_IN_TEMPDB = ON, ONLINE = OFF )
" failed with the following error: "The transaction log for database 'SharePoint_Collab1' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases
The statement has been terminated.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
Any advice?
April 12, 2011 at 8:07 am
Sqlsavy (4/12/2011)
failed with the following error: "The transaction log for database 'SharePoint_Collab1' is full.
I usually run transaction log backups in between index rebuilds.
Read: Why is my transaction log full?
By Gail Shaw
http://www.sqlservercentral.com/articles/Transaction+Log/72488/
April 12, 2011 at 9:24 am
Thanks Gail
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply