I'm about to start using SQLMaint, instead of manually executing all the
check tables, text, sysindex stuff that I'm scheduling now.
Here's an example of the SQLMaint parameters that I want to run:
SQLMAINT.EXE -D loopdb -CkDB -CkAl -CkTxtAl -CkCat
-UpdSts -RebldIdx 10 -BkUpDB D:\LOOPDEV\BACKUP
-BkUpDB -BkUpMedia DISK -DelBkUps 4 -Rpt
I plan to run this every night. My database is only 90 megs (including
indexes and everything), but it represents the life * of the
company, so it would be nice if I could ensure that it doesn't break, or
that if it does we can get something sensible restored.
When I run this command it takes only about 5 minutes to execute, so I
feel ok about running it every day, in terms of load on the server. Are
there any negative experiences that people can relate concerning the use
of DBMain instead of manually executing ISQL statements?
The -RebldIdx 10 statement I'm not sure is correct. Is 10% a reasonable
size? What does this mean anyway, and how should I calculate a correct
number? I stole this value from the SQL Database maintenance wizard that
I ran on a test database. My tables grow at less than 2% per day in
general, and most don't grow at all.
Insert and update speed is a very low priority for the operation of the
company and this database (select speed is much more important).
I suppose I've got a good situation in that the database activity is
reasonably low, the server isn't over loaded and the tables don't grow
very fast, but since the data are important, I'm trying to do everything
I can to ensure I have good backups and integrity.
Any advice or suggestions would be appreciated.