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 |
|
davidagnew37
Starting Member
33 Posts |
Posted - 2004-08-25 : 07:00:59
|
| Hi, We currently have a fairly new SQL server 2000 db (currently about 18mb is size) as a backend to an application (Navision). Performance seems to be below what it should be. I think this may be due to our initial file properties. The db is increasing quite rapidly in size, with a lot of data scheduled to be loaded onto the db and also more and more shops and users coming onto the system with alot more transactions going onto the db. The initial setup of the db has the database File properties set to "Automatically grow file" by "30%" and has an unrestricted file growth. The server that the db sits on is high spec and very large disk space.Because the database will be expanding alot and thus reaching its maximum space allocation and then performing a 30% increase in size (which I guess affects performance quite a bit??) quite regularly. Is it best to set the intitial size of the db to a alot bigger size in the first place as we have large disk space availiable and also set the % increase bigger also. any advice on best performance would be much appreicated. Regards,David |
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2004-08-25 : 07:35:49
|
| It's best to estimate what your file size will be in (for example) the first 3 months and set it to that. I would have your increase size set to 10% or 15% after that though. 30% increase is a lot and will consume resources while it's taking place.MeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
 |
|
|
davidagnew37
Starting Member
33 Posts |
Posted - 2004-08-25 : 08:42:36
|
| thanks Derrick. |
 |
|
|
|
|
|