Video Screencast Help
Give us your opinion and win with Symantec! Please help us by taking this survey and tell us about your satisfaction level using Symantec Connect. One lucky winner will receive 500 Connect points!* Take the survey.

Connect FG_ size settings to DB Log Settings

Created: 04 Mar 2013
sep_tx's picture
0 Agree
1 Disagree
-1 1 Vote
Login to vote

It is not clearly documented or made obvious to the admin that there are various default sizes for various files in the database.

One would assume that after going through the sizing guide and other data provided that the sizes are associated to the 'Log Settings' under 'Database properties' and the 'LiveUpdate' settings under 'Site properties'.  This is of course why the admin was warned about minimum specs and harddrive size etc.

For those administrators that chose to keep an above average number of content revisions (or log rows) in the first place it would be super handy if the modification of the 'Log Settings' and 'LiveUpdate' settings would call a function to automatically increase the 20GB default size of the various associated FG_ files.

For example default revisions are set at 10, default FG_CONTENT is set at 20GB, if the administrator raises the revisions to 20, the FG_CONTENT should automatically increase to 40GB.   At the very least a note should be made somewhere in the documentation and/or sizing guide that in large environments the administrator may want to look at FG_ settings for databases that are expected to be very large.

KB article is helpful but it would be nice to avoid this all together rather than find it after receiving error messages.