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 |
gnobber
Starting Member
11 Posts |
Posted - 2009-06-14 : 00:08:29
|
Hi,I just want to ask what are the guidelines regarding initial size and autogrowth when strating to create a database? |
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2009-06-14 : 11:21:49
|
Depends on what future growth pattern is designed for the database. |
 |
|
SQLRatankalwa
Starting Member
42 Posts |
Posted - 2009-06-16 : 08:44:05
|
You need to calculate the size of the database and the growth in the next year to 3 years, also understand how your log will grow and also how the tempdb is going to be effected, based on which you can actually size the database, log and also the tempdb. Every time autogrowth happens on the log or the database size increases, then there will be an effect on the performace.Ratan KalwaSQL Server Professionals User Grouphttp://www.revalsys.com |
 |
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2009-06-16 : 10:20:02
|
Having a small initial size (i.e. creating a default database then expanding it) means that a lot of the system objects will be created for a small database. It's better to create with a larger initial size.As to autogrowth - depends on the system and how it's controlled. It would be best to expand manually so you are in control of when it happens - but that means that you have to control everything that runs and is released. It is quite common for someone to release something that temporarily uses a lot of data or log space - do you want that to bring down your system or just degrade the performance in the hope it will complete.There's no answer, it depends on your system. I tend to put a large max size on databases and keep a daily record of usage.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
|
|