Reputation
Top tag
Next privilege 200 Rep.
See reduced ads
Badges
8
Newest
 Commentator
Impact
~2k people reached

  • 0 posts edited
  • 0 helpful flags
  • 3 votes cast
Oct
27
comment First log backup after FULL taking lots of space
Thank you all. That was the problem. I've changed the Index Optimize to execute once a week only and with other parameters as described here: brentozar.com/archive/2014/12/… Now the LOG took around 100mb the first day after change.
Oct
27
accepted First log backup after FULL taking lots of space
Oct
23
comment First log backup after FULL taking lots of space
Answering my last question :) brentozar.com/archive/2014/12/…
Oct
23
comment First log backup after FULL taking lots of space
Thank you guys. I would not like to make those changes during the weekend as I don't want to have to fix it on a Sunday, but I'll test it next week. I wonder how should I tweak it if this is the cause (very likely as now I understand how it works). Doc from Ola Hellengren: ola.hallengren.com/…
Oct
23
comment First log backup after FULL taking lots of space
Got it thanks. I was wondering if it's possible to avoid having those huge LOG backups. Doing a LOG backup after the Index optimize would not avoid that but it would speed up restores since that last LOG will be most of the time not needed.
Oct
23
comment First log backup after FULL taking lots of space
Thanks. If that's the case (I'm going to test it during the week). What would be the solution to be able to do a IndexOptimize and now having the log backup be huge? I'm running LOG backups from 6:30am until 4:30am next day to avoid it running at the same time the FULL backup runs. I'd appreciate if you can extend your answer and tell me how to configure/schedule it right. Thanks.
Oct
23
awarded  Commentator
Oct
23
comment First log backup after FULL taking lots of space
@srutzky if that's happening I couldn't say why. If the IndexOptimize is being executed before the full backup, then the full backup should have those changes and the next log backup only the changes made after the full backup. I might be wrong though :)
Oct
23
comment First log backup after FULL taking lots of space
@AliRazeghi all LOG backups are under 700mb. The one before the FULL backup was around 50mb the last couple days. The one right after the FULL backup is 6-9GB
Oct
23
comment First log backup after FULL taking lots of space
@PJMahoney I've added more info. Process-CT-Cube does not work in that database.
Oct
23
revised First log backup after FULL taking lots of space
added more info
Oct
23
comment First log backup after FULL taking lots of space
@AaronBertrand forgot to include the screenshot. Take a look. The full index optimize, DB check and full backup takes 37'
Oct
23
awarded  Editor
Oct
23
revised First log backup after FULL taking lots of space
Corrected time.
Oct
23
asked First log backup after FULL taking lots of space
Nov
26
awarded  Autobiographer
Aug
14
awarded  Popular Question
Sep
28
comment What does “*password------------” mean in a profile deadlock report?
Thanks @MartinSmith, in my case it's not attack, I have a users table with a password field. Thanks again! =)
Sep
28
awarded  Scholar
Sep
28
awarded  Supporter