>
> Someone wrote
> >>
> ... we backup & restore because in the past the database stated to
> become slow, and a backup - restore actions seems to solve it. so we
> started to backup and restoring as well, this seems to keep the
> database faster and smaller.
> Is there another way ?
> >>
>
> How often do you (any of you!) restore backups as part of regular
> maintenance?
> I don't mean just a restore to check whether a backup is valid, but
> to create a new "fresh" database free from any accumulated crud.

annually minimum. sometimes 6 months. Our DBs are set to log everything
internally so they grow a lot. I need to remove the log data every so often
and that's what prompts me to do a restore (replacement) cycle.
Alan

>
> I see that three years have passed since my last restore of my "main"
> database (at about 3GB), and I'm wondering if I should replace the
> production version with a newly restored one.
> Is there a general consensus? E.g. don't fix something that isn't
> broken or some such. An alternative for me could be just to refresh
> the indexes since no "slowdown" has been observed.
>
>
> --
> Aage J.
>