anorthcote
Programmer
Hi,
My database runs a weekly import job followed by several stored procedures to re-format and calculate on the imported data. This job has been running weekly for a couple of years now without any problems.
The data I import each week has grown a lot over the last few weeks and I am now getting the following error on setp 58 of my sheduled job
I am running this job at 6:15 on a Sunday morning and have the maintenance job running at 2:00 on the Sunday morning. I would have thought that running the maintenance job before my scheduled job would have cleared the transaction log sufficiently. The scheduled job I have does do a lot of processing and I have re-written the step it is erroring on to make it more efficient but I'm still getting the error.
My HDD space is not short so how can I extend the transaction log or do something to stop it erroring. My recovery is set to simple as I don't need the trasaction logs to recover the database. I don't understand what is going on!
My database runs a weekly import job followed by several stored procedures to re-format and calculate on the imported data. This job has been running weekly for a couple of years now without any problems.
The data I import each week has grown a lot over the last few weeks and I am now getting the following error on setp 58 of my sheduled job
Code:
Msg 9002, Sev 17: The log file for database 'SZ' is full. Back up the transaction log for the database to free up some log space. [SQLSTATE 42000]
I am running this job at 6:15 on a Sunday morning and have the maintenance job running at 2:00 on the Sunday morning. I would have thought that running the maintenance job before my scheduled job would have cleared the transaction log sufficiently. The scheduled job I have does do a lot of processing and I have re-written the step it is erroring on to make it more efficient but I'm still getting the error.
My HDD space is not short so how can I extend the transaction log or do something to stop it erroring. My recovery is set to simple as I don't need the trasaction logs to recover the database. I don't understand what is going on!