rapidly growing log file

Question

rapidly growing log file

Viewing 8 posts - 31 through 37 (of 37 total)

You must be logged in to reply to this topic. Login to reply

Mayank Khatri SSCertifiable Points: 7984 More actions · Answer 1

So even if u SHRINK ur file, it will grow back to 7 GB again later on. U should make sure the queries running have transactions closed i.e. for every BEGIN TRAN there SHOULD be CLOSED TRAN or ROLLBACK TRAN

Steve Jones - SSC Editor SSC Guru Points: 736078 More actions · Answer 2

truncate the log (backup with truncate only) and see if it grows again. Check the logspace (as shown above) regularly.

Mayank Khatri SSCertifiable Points: 7984 More actions · Answer 3

Steve Jones - Editor (5/21/2009)
truncate the log (backup with truncate only) and see if it grows again. Check the logspace (as shown above) regularly.

Steve, I think his database is in Simple Recovery model so WITH TRUNCATE_ONLY option will not work

Steve Jones - SSC Editor SSC Guru Points: 736078 More actions · Answer 4

Right, sorry, Flip to full, truncate to clear space, flip back.

I want to reset the space usage down and see what happens.

Jeffrey Williams SSC Guru Points: 90303 More actions · Answer 5

Steve Jones - Editor (5/21/2009)
Right, sorry, Flip to full, truncate to clear space, flip back.
I want to reset the space usage down and see what happens.

No need to truncate the log. Switching to FULL and then back to SIMPLE will accomplish the same thing.

Remember, that functionality is deprecated in 2005 and is non functional in 2008.

Instead of doing that, manually issue a checkpoint to force the dirty pages to be written to disk. In simple recovery, you might need to issue this a couple of times to force a rollover to the beginning of the file.

Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”

― Charles R. Swindoll

How to post questions to get better answers faster
Managing Transaction Logs

doug turner SSChasing Mays Points: 657 More actions · Answer 6

Thanks for all the help guys. I took some time off this weekend, came back and the log file is now up to 10Gb and the database is up to 1.5Gb. Now I have another issue I need to post on. Replication issues. Geez, if it isn't one thing with this database, it's another!

Mayank Khatri SSCertifiable Points: 7984 More actions · Answer 7

Is the replication issue with the same database?

Is ur database set in replication(If yes then what kind)?

doug turner SSChasing Mays Points: 657 More actions · Answer 8

Yes, it's the same database. I'm trying to replicate into and another database on the same sever, but only grabbing a few fields from the source. It's posted under replication error to keep this thread clean.