Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
bharath63
Starting Member
14 Posts |
Posted - 2009-03-17 : 07:39:26
|
Hi,We had databases Log file Intial Size set to 1 Mb and autogrowth set in 10 Percentage to grow. Then later we changed the Intail Size of log file to 100 MB. But after few hours it is set back to 1 MB leading back to old problem. Is it because auto shrink is set on databases.I have come with an alternative but not yet implemented, to set autogrowth by 100 MB Size so even if the Log file is set back to 1 Mb it will again reach 100 MB giving Log space more room. Am I right on this??Database recovery model is FULL.BHARATH |
|
mfemenel
Professor Frink
1421 Posts |
Posted - 2009-03-17 : 09:11:41
|
I would reccomend against using auto shrink. This is not a good practice because auto shrink can happen at anytime and usually when you're at your busiest. This can cause performance issues which you have no control over. Before you set your auto growth to a specific size I would get an idea of what your average growth per day is so you can make an educated adjustment rather than a shot in the dark that 100 mb is the right number.Mike"oh, that monkey is going to pay" |
|
|
tosscrosby
Aged Yak Warrior
676 Posts |
Posted - 2009-03-17 : 10:53:17
|
To add on to Mike's reply, if autoshrink occurs, there is a real potential for fragmenting your indexes as well (if it's the data file being shrunk), leading to even more performance issues. If autoshrink is on, I personally would turn it off.Terry-- Procrastinate now! |
|
|
bharath63
Starting Member
14 Posts |
Posted - 2009-03-18 : 09:40:18
|
I agree with your thoughts and will consider turning off auto shrink. But my douts still remains why did the Log file size reduced back to 1 MB when I had set the intial size to be 100 MB and I used TSQL scripts to increase the file size.BHARATH |
|
|
|
|
|