"Jeffrey Sheldon via SQLMonster.com" <fo***@SQLMonster.com> wrote in message
news:5a******************************@SQLMonster.c om...
Just wanted to know what is a general rule of thumb when determining log
file space against a database's data file.
We allow our data file for our database to grow 10%, unlimited. We do not
allow our log file to autogrow due to a specific and poorly written
process (which we are in a three month process of remove) that can balloon
the log file size.
Should it be 10% of the Data file, i.e. if the Date file size is 800MB the
log file should be 8MB?
I realize there are a myraid of factors that go against file size but a
general starting point would be nice.
Thanks
Jeff
--
Message posted via http://www.sqlmonster.com
I don't believe there's any MS recommendation on this, although I'm happy to
be corrected. I think I read a post from an MVP saying he uses the size of
the largest table plus 10%; personally, with no other information to base a
decision on, I would go for 20% of the size of the data file(s). But as you
say, there are a myriad of factors, so you may as well just pick a number
(do you have another similar database to compare against, perhaps?), and
then adjust it as you go along. Beware of auto-grow/shrink, though, which
can be a bit of a pain if it kicks in at the wrong time - it's probably
better to go with a fixed size and too large rather than too small,
especially since disk space is relatively cheap.
Simon