April 1, 2005 at 5:00 am
All:
I'm trying to figure out a couple things.
1) My log grows to something like 45 GIG when we run a re-index job and the original database is only 42 GIG. In addition, the recovery mode is set to simple. Thats only the first problem.
2) I issue the following command today to try to truncate the log (BACKUP LOG <DBNAME> WITH TRUNCATE_ONLY
When I did this, I received the following messages:
Server: Msg 3023, Level 16, State 3, Line 1
Backup and file manipulation operations (such as ALTER DATABASE ADD FILE) on a database must be serialized. Reissue the statement after the current backup or file manipulation operation is completed.
Server: Msg 3013, Level 16, State 1, Line 1
BACKUP LOG is terminating abnormally.
No jobs seem to be currently running (like a backup or anything) and yet I cannot truncate the logs.
Does anyone have any suggestions?
April 1, 2005 at 5:47 am
Try later. It seems something is going on which stops your command.
April 1, 2005 at 5:51 am
Yeah, I think I found out what is causing it. Our hosting provider is running backups well past their window. Not sure why yet, but at least I know the WHAT. They don't run it via job, so I didn't see it until I looked more closely at our process list.
Thanks to all!
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply