george sibbald (11/5/2012)
For the data file I would say about 100MB, certainly avoid growth factors stored as a percentage. For the log file a growth factor of 64MB. As for what size it should be that depends on a number of factors, recovery mode mainly. what is your log backup strategy? if you take log backups whats the frequency and size of the largest log backup?read this
The data file and the translog file are set to Auto grow, by 10%; I'll change them and keep an eye on the growth. They're also both set to Unlimited file growth. (This DB was originally set up by the vendor and I figure they just went with the defaults.)
The current Plan backs up this DB every evening at 10:15pm; I've set the translog to get backed up once each hour during the workday (between 9am-6pm). The largest translog backup is just over 2GB, the others of course much smaller, between 2 and 35mb. The DB recovery model is Full.
it will be, its just that the work done by the reindex would have been ruined by the shrink, which fragments indexes as it just attempts to move data to the front of the file without taking into account what object that data relates to. Your largest amount of log activity will be when the reindex is run.
Is the "Reorganize Data..." task on the Optimizations tab the same as reindexing? (It's checked right now and set to "Change free space per page..." to 15%.) I don't see a specific option for reindexing?
Thanks again for your help and suggestions!
Tom