Autogrowth is enabled by default for the SQL Server database files. The default setting of 10% for file growth on the database files can often times lead to poor performance, especially if you don't properly size your files for the near future.
An example of when you'll see poor performance is when you have a database that is 500GB in size. When it runs out of free space, it'll autogrow by 50GB. Depending upon your disk performance, this could take a bit of time to allocate the space which could impact your end-users. To minimize the impact, change the file...
EDIT: There is a new version of this stored procedure.
I've made a couple of changes to my defragment indexes stored procedure, isp_ALTER_INDEX, based upon feedback I've received from my blog readers. For those unfamiliar with this object, it defragments indexes in SQL Server 2005 using the ALTER INDEX command. Check the comment header block for its documentation.
Here are the changes:
Added support for database and object names with special characters.
Added support for indexes with the ALLOW_PAGE_LOCKS option enabled. Online reindexing is not available for indexes with this option enabled.