July 8, 2004 at 10:20 am
The log file for database 'DB' is full. Back up the transaction log for the database to free up some log space. [SQLSTATE 42000] (Error 9002). The step failed.
The job was doing insterts when it failed. I see no roll back in the code of the stored procedure. Questions:
What can I do for the log?
Is a roll back automatic with such an error
July 8, 2004 at 11:08 am
Move the log to another drive with sufficient disk space to allow for all the inserts to happen.
Alternatively you could change the recovery model to simple, that's something you would have to decide on with regards to the recoverability of the data.
You can also shrink the log initially with backup log ? with no_log; dbcc shrinkfile (?, 1, truncateonly) (replace the ? with appropriate values)
July 9, 2004 at 1:43 am
Go to the Em Select the database file goto properties.
set the recovery model simple.
now goto em all tasks shrink database , select files select the log file and shrink.
--Jeswanth
--------------------------------
July 9, 2004 at 6:04 am
I have had this message a couple of times since applying SP3 to SQL2K.
We have massive free disk space (40GB+) and only a small logfile on tempdb (200Mb).
I have seen a number of other people post similar messages on the web and the consensus seems to be that this can be a spurious message in that the queries causing the message run to completion without error an the log file grows after emitting the error. The message may be avoided by increasing the file growth percentage increment.
If you still have free disk on the device that holds tempdb log look at this:
See http://www.devdex.com/sql/message.asp?p=&r=4282263&page=2
July 9, 2004 at 12:51 pm
I am on sp3. I'll take a look. Thanks
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply