I was kind of surprised by this one.It's a 70GB database. The standard policy in question is to create a maintenance plan to execute once a week with a reorganize index task (with compact large objects option... it's SQL 2005), followed by an update statistics task (with all existing statistics and full scans).This results in a lumpy 50GB log backup within the hour; which is ~70% of the data size. 1. Is that a lot? It seems excessive to me. I wouldn't know though seeing as most places I've worked at use a competent strategy to only rebuild what's necessary.2. Aside from suggesting we switch to Ola's scripts (not going to happen in the short term), is there a Maintenance Plan-eque way to reduce this?
↧