March 13, 2006 at 5:31 am
Hi
I have a small query about the autogrow of files in SQL.
First of all what is the correct way out--Unrestricted File growth or Restricted File growth??
If I have unrestricted File growth then it should be in Megabytes or Percentage--Which is better??
When does the database files grow automatically..What is the minimum sapce after which the data files grow??Does the autofile growth hampers the normal functioning and querying on the server..I mean when this is happening will it have any effect on the production or not??
March 13, 2006 at 5:51 am
You will probably get a few different views on this but for my servers.
Restricted file growth - I dont want the server going down because the os has run out of space.
Autogrow by a fixed amount not a percentage.
Autogrow is expensive and a production database will take a performance hit as it autogrows. Best practice would be to size it so that it would never have to autogrow. If freee space is getting low then resize it yourself at the quietest (database) time
March 13, 2006 at 6:15 am
I would allocate a chunk of space based on projections for the next couple of years. This way the db would not auto grow.
You can setup alerts to email you when your server is running out of space.
March 13, 2006 at 8:10 am
Definitely fixed growth.
I would try and size it so that an autogrow isn't going to happen unexpectedly.
I would also check out the settings for TEMPDB. Unless you have changed it then the default TEMPDB size is 8MB on startup.
After taking advice on this forum I changed mine to the following
1. A file per processor
2. Fixed growth
3. Equal size per file.
4. Quite large (4GB each).
March 13, 2006 at 8:18 am
hi
Should we have fixed growth for the transaction file also.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply