October 24, 2014 at 7:58 am
I have a job that is failing with 'log full' (9002). The db is SIMPLE, the log file is actually quite large (15G) for a simple db (historical reasons).
The actual transactions shouldn't (I think) be causing an issue, a table is TRUNCATEd, then a copy command to bring rows over from a linked server (SELECT INTO ... ). There is no processing of data involved.
'log_reuse_wait_desc' = 'NOTHING'; log file free space is about 99%
Any thoughts?
[BTW the total rows of all 28 tables is only about 20M rows]
...
-- FORTRAN manual for Xerox Computers --
October 24, 2014 at 8:29 am
Something in the job is filling the log, failing and rolling back, leaving the log empty again after it completes.
You're going to have to monitor log reuse reason and % full while the job runs to diagnose why the log is filling.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply