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 |
|
MichaelP
Jedi Yak
2489 Posts |
 Posted - 2006-03-22 : 19:57:11
|
| I'm looking for some "best practices" on database file growth. The default is 10%, but many of our databases are 50GB+ so growing at 5GB at a time is not very user friendly. From my reading and research, I've seen reccomendations in the 100-200MB fixed growth. I think that will be much more user friendly, but I'm a bit concerned about fragmentation and the frequency of said growth. Another option is set it to a small fixed size growth, and do periodic large growths (5-10GB at a time) at off peak times. This will allow us to "schedule" when the system will be under load due to file growth.Is there anything I'm overlooking? I'm open to suggestion here! Thanks!!Michael<Yoda>Use the Search page you must. Find the answer you will. Cursors, path to the Dark Side they are. Avoid them, you must. Use Order By NewID() to get a random record you will.</Yoda>Opinions expressed in this post are not necessarily those of TeleVox Software, inc. All information is provided "AS IS" with no warranties and confers no rights. |
|
|
Westley
Posting Yak Master
229 Posts |
Posted - 2006-03-22 : 23:29:46
|
| Hi, Not sure if that is the best practices, but here is my 2cent. What we normally do is have some report going to monitor the growth of DB, and we set it up so that it normally have like 20-30% more free space then it needs, we do allow auto growth just incase if anything big comes in, but do have a limit size in case it just kills the server. but once the free space goes down to some predefine size, say 5%, then we manually add the big chunk of size to it, say in ur case, 5Gb - 10Gb. This way it will never run out of space, and you always in control. :) |
 |
|
|
|
|
|
|
|
Database file growth reccomendations