|
Home > Archive > MS SQL Server > July 2005 > Suggested "Maintenence Routine"
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Suggested "Maintenence Routine"
|
|
|
| How often (other than daily backups and hourly Trans Logs Backups) should
maintenence tasks be run on low - moderatle use sql db. Our DB is 6GB and we
have 4 heavy users (order entry/posting payments etc) and 14 light
(inventory/customer lookups, product lists etc)
Is it recommended to run integrity checks, optimize and update statistics
every day? If not how often.
Full Backups happen every night (to both external disk AND tape), log files
are backed up to separate external disk hourly and taken to tape both
overnight and again at end of day.
MM
| |
| Hari Prasad 2005-07-28, 3:23 am |
| Hi,
Looks like your maintenance plan schedule is good. But I recommend you to
schedule the transaction log backup every 30 minutes.
Is it recommended to run integrity checks, optimize and update statistics
every day?
Executing integrity checks and update statistics daily is a good practice.
Thanks
Hari
SQL Server MVP
"M.M." <nosend2me@hotmail.com> wrote in message
news:OQ3R9ExkFHA.2156@TK2MSFTNGP14.phx.gbl...
> How often (other than daily backups and hourly Trans Logs Backups) should
> maintenence tasks be run on low - moderatle use sql db. Our DB is 6GB and
> we
> have 4 heavy users (order entry/posting payments etc) and 14 light
> (inventory/customer lookups, product lists etc)
>
> Is it recommended to run integrity checks, optimize and update statistics
> every day? If not how often.
>
> Full Backups happen every night (to both external disk AND tape), log
> files
> are backed up to separate external disk hourly and taken to tape both
> overnight and again at end of day.
>
> MM
>
>
| |
|
|
|
|
|