October 12, 2009 at 5:53 am
My optimization job runs once a week after that my logs are too big, is there way to do something about it? We are running out of space, because we do back back up every day and then full back up oonce a week
October 12, 2009 at 6:14 am
Are you talking about the transaction logs?
Try backing the tran logs up more often than once a day. Try switching the DB to bulk-logged recovery for the duration of the index rebuilds, then back to full (and take a log backup) afterwards.
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
October 12, 2009 at 10:48 am
I do transaction logs every 4 hour.What happends after I run my optimization job at 5:00. My transaction logs at 8:00 get really big almost the same size as reg.bakup and then at 12:00 gets back to normal, when I ran my reg full back it is really big and we are paying a lot of money for backup. What is your suggestion? Thank you
October 12, 2009 at 10:59 am
Krasavita (10/12/2009)
What is your suggestion? Thank you
GilaMonster (10/12/2009)
Try switching the DB to bulk-logged recovery for the duration of the index rebuilds, then back to full (and take a log backup) afterwards.
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 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply