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 |
|
harlingtonthewizard
Constraint Violating Yak Guru
352 Posts |
 Posted - 2010-03-18 : 21:06:52
|
| As a rule of thumb how does one select what the Database initial size and file growth settings should be? How dow the file growth affect performance? |
|
|
Lumbago
Norsk Yak Master
3271 Posts |
Posted - 2010-03-19 : 08:36:03
|
| I can't remember reading any best practices for initial size but I held a crash course in installing databases a few weeks back and I said that the initial size of the database should be twice as large as the amount of data you expect to insert within the first year. In other words: if you expect the database to be roughly 1GB after the first year, your initial size should be 2GB.File growth is somewhat more difficult because it depends on the growth factor of your data which is usually hard to predict. File growth *should* be controlled manually due to the impact it has on performance, but if you don't plan to monitor the database that carefully the default 10% is fair enough, but it's generally recommended to use a fixed increase in MB. It really depends on the usage though...- LumbagoIf the facts don't fit the theory, change the facts. Albert Einstein |
 |
|
|
Kristen
Test
22859 Posts |
Posted - 2010-03-19 : 09:21:29
|
| I would always use fixed increase in MB, never a percentage. I'm happy with a size increase that is good for a month or so.We use a defrag program to make the file allocations contiguous. (CONTIG from SysInternals, now owned by Microsoft).Are there any side effects of the database having created, possibly, numerous extensions once they are made into a single contiguous extent? |
|
|
|
|
|
|
Database initial size and file growth