Hi there Bill

1) I grow my the Mb over %, the larger the db the worse this figure is,
Monitor your space util over time and alter accordingly.

2) As above, but take care with this - pre grow the files to accommodate
their typically daily usage, ops like dbcc reindex will blow out the file
size from your standard daily work (usually).

3) Full or Bulk Logged (read up the BOL) - with either you need to run
transaction log backups otherwise your trans logs will never stop growing
with completed trans ready for archiving (the backup). I would do a full
each night then tran logs each hour, its all a business need though and if
it's a very large dbms the times and types of will of course vary.

4) Ifs it's a dedicated box, I would set memory to a max of 15 to 20% less
than the total memory on the server. Set audit level to "on failure". Rest
is fine, perhaps worth while entering the new default db dirs up to an
appropriate dir.

Cheers

Ck
www.chriskempster.com

MS Sql Server LazyDBA home page