Would you mind to share with me what is typical job that you guys running as day to day db maintenance. I am trying to comparing with ours.
Here's what we configure so far in SQL: 1. Secondary DB Backup to File Server (primary is done through Veritas NetBackup) - every night 2. Primary Transaction Log to File Server - every hour. (sometimes depending on the database .. normally we used Veritas NetBackup) 3. Integrity Check - Saturday midnight 4. Optimazation (Reorganizes data and index pages AND Remove Unused space from database files) - Saturday midnight 5. Usage Update - wednesday night 6. Cycle Error Log - Sunday midnight
Those jobs (1-5) were associate with each user database while System databases is combined into for each job.
BTW ... we did this through Database Mainteanance Plan. We are thinking to move to script instead which I believe is more control.
Thanks for sharing.
Edited by - dewacorp.alliances on 08/25/2006 11:43:14
Depends on the system. I have a client at the moment where there are no backups or integrity checks - and that's fine for their system. Have another with daily full backups, diffs throughout the day and log evey 10 mins. All full backups restored to another server and integrity checked.
It's up to a dba to decide what's needed for the business (should be part of a business continuity plan) - you can't generalise.
========================================== Cursors are useful if you don't know sql. DTS can be used in a similar way. Beer is not cold and it isn't fizzy.
DHave another with daily full backups, diffs throughout the day and log evey 10 mins. All full backups restored to another server and integrity checked.
Hi nr. You mentioned about "All full backups restored to another server". So you have a job as well for restore on the other server so it's some sort of Database Shipping ... correct?
========================================== Cursors are useful if you don't know sql. DTS can be used in a similar way. Beer is not cold and it isn't fizzy.