January 15, 2009 at 9:44 am
I just wanted to know that what is the difference between Creating Database with minimum size and let it grow with 10%
and Creating a database with big size in the begning,
Will it affect the performance, if we let if grow automatically.
January 15, 2009 at 9:49 am
When a database has to grow due to a transaction, it has to request the space from the operating system and then expand the file. This can be a relatively slow process, so it should be avoided.
A database can never shrink to less than it's initial size.
So, I like to create databases with a very small size for each file. I then increase the file size to accomodate our needs for about 6 months. Then, I schedule a reminder for myself to re-evaluate the database size in six months and expand the file again manually. I do allow the databases to auto-grow, but it is best to anticipate the growth and do it manually ahead of time.
January 15, 2009 at 9:50 am
Autogrows will HALT all activity until disk space is allocated. 10% may not seem much when sizes are small it can be a big deal for large sizes or very intense activity.
You should use autogrow as a fail-safe feature and grow your files manually at planned off-peak times.
Cheers,
* Noel
January 15, 2009 at 10:08 am
Thank you all for the reply.
I created lots of partition tables and filegroups and assigned inital size to the filegroups but now all the filegroups are not 100% full , some are 30% and some are 40% full, comsuming lots of hard disk space and I know that those filegroups will never get filled in futre becuase of the date range.
I think , it makes sense to shrink all the filegroups except current filegroups becasue data is still filling in it.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply