August 22, 2013 at 4:13 pm
I have found some of my databases that have high vlf counts.
It looks like the ones that had the high count have had either small increment growth settings or the setting was set to grow as a percentage.
I have now adjusted the Log files to the correct size after following Kimberly Trips advice
http://www.sqlskills.com/blogs/kimberly/transaction-log-vlfs-too-many-or-too-few/
My question is do i now need to back up the msdb databases on the servers i made the changes too, as our servers get rebooted every month, to keep the new growth settings intact ?
August 22, 2013 at 4:17 pm
no, that information is not kept in the msdb database.
the only thing that would revert the settings is restoring from a backup of the database before the change.
---------------------------------------------------------------------
August 22, 2013 at 4:25 pm
ok thank you for the quick reply.:-)
August 22, 2013 at 4:28 pm
no probs. Eddie Vedder is it?
---------------------------------------------------------------------
August 24, 2013 at 12:22 am
Ha ha!!! Not quite. If I was Eddie V I wouldn't have to be working with sequel - I'd be surfing the ocean not the Internet for SQL answers!!! Lol!
Thanks again.
August 24, 2013 at 4:28 pm
PearlJammer1 (8/22/2013)
I have found some of my databases that have high vlf counts.It looks like the ones that had the high count have had either small increment growth settings or the setting was set to grow as a percentage.
I have now adjusted the Log files to the correct size after following Kimberly Trips advice
http://www.sqlskills.com/blogs/kimberly/transaction-log-vlfs-too-many-or-too-few/
My question is do i now need to back up the msdb databases on the servers i made the changes too, as our servers get rebooted every month, to keep the new growth settings intact ?
As George pointed out, the settings aren't stored in the MSDB database. Most of the time, if you do a full restore, the settings will come in with the database, IIRC. The settings are, however, stored in the Master database and there are instances of where the settings in the Master database would be used, particularly for TempDB on a reboot but for other databases as well (I just can't put my finger on when that would occur, just now).
My recommendation would be to make sure that you backup your system databases at least once a night. They're not very big and they don't take much time too backup but if something goes haywire, having recent backups on the system databases can save your butt.
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply