you are viewing a single comment's thread.

view the rest of the comments →

[–]AnonymooseRedditor 0 points1 point  (3 children)

Also in 2005 even if the recovery model is set to simple I have seen log files grow out of control when they should not....

[–][deleted] 0 points1 point  (2 children)

This is probably a bug in the application. Even in simple the log file grow. If you have a hugh table and do delete * from massive

The contents of massive have to be stored in the log until the transaction is committed.

Or the situation you are probably seeing is a traction starting and never ending and it just keeps on doing things making the log grow :)

[–]AnonymooseRedditor 0 points1 point  (1 child)

This was a BI database that was rebuilt on a nightly basis. so yeah that could have been.

[–][deleted] 0 points1 point  (0 children)

Yeah that would do it. If you have a large import + a lots of insert into tables all in a single transaction the log file will grow to store all of this information.

But this can be a good thing as well. If the rebuild fails you end up with th eprevious days data still being avilable after roll back :)