kaplan71 (12/3/2012)
Hello --One of our systems is running SQL Server 2005, and has a database that was initially 'sized out' at thirty, 30, gigabytes. The space that is currently taken up by the database is twenty-nine, gigabytes. We are at a point where resizing the container available to the database is a necessity, and I need feedback on the following:
We can either manually resize the database to fifty, 50, gigabytes, or let the server automatically do the resizing. The database will continue to grow, but giving it the aforementioned space will give us over three years before we need to consider resizing it again. I am of the opinion the manual approach is the way to go in this scenario, but I wanted to get feedback on this.
Prior to doing this, we will do a full backup of the database, and after the resizing is done, we intend to run the database consistency checker to verify the change made did not adversely effect it.
That's a good plan to manually increase the data size in the production server. But if you have more than 100 servers you can't do it for all servers.
The only thing you've to consider is database file sizing is costly operation. Consider you apply on non peak hours. Restrict your file growth 8 GB or less.
File sizing is a harmless operation. But if you prefer, you can do consistency check on database.
-- Babu