June 25, 2014 at 3:25 pm
This is my dilema, just took over at shop no dba for a while have and upgrade to a 3rd party database this weekend. Upgrade is a mountain of scripts done in a gui. Several of the data files (mostly index files) are set to a restricted growth and some are almost out of space. A little worried about upgrade scripts causing issues with running out of space. I am thinking about for the weekend to set all these files to autogrow unlimited. Any think this is a bad idea. Been doing this for years and pretty much committed to unrestricted growth unless someone convinces me to a better solution
June 25, 2014 at 6:17 pm
As long as you are monitoring overall disk space and have reports on database growth (optional) you should be fine.
Make sure growth increment is not set to default.
In general however if you have the luxury of doing capacity planning, yo want to pre-grow your databases to some expected size.
June 26, 2014 at 3:13 am
If they're low on space, yeah, I'd turn on auto grow, or maybe just go ahead and give them some head room now if you have the disk space to spare.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply