April 15, 2010 at 2:35 am
Hello,
I have a question about the autogrowth on on databases, there is something I cant quite get my head around. If a database is created and everything is left as default the autogrowth might be something like by 10% and the restricted growth ends up at something like 2097150 for the logs with the initial size being 2GB, what I am wondering is, if you have regular log backups so the logs are never really larger than say, 100mb what difference does it make to bring the restriction down to something like 300mb? What is the benefit of restricting the logs size?
I expect these are basic questions, I did have a look around the web but didnt really get a clear answer.
Regars,
D.
April 15, 2010 at 3:06 am
You can restrict file growth, but think about new picture like if your backup fails and your log file reach 295 GB or your team doing some BCP operation and file grows 295 GB and BCP completed 90%, that time your database you database log is full and no one can fire any query because your log file is full.
April 15, 2010 at 3:13 am
Hi
One consideration could be about the transaction volumes of your application. If it is transaction intensive , your logs could fill up before they are backed up and stop the database from responding. If you try to increase the frequency of log backups it might take a toll on the server. I agree to the idea of restricting the log but you should try to keep some extra space based on above observation.
Regards
Parikshit
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply