Hi dudes!
I agree with Mushtaq_M that you can shrink your files, and also that this is not recommended; some DBAs become very nervous if they see some tens of Gb allocated by the database but free and which space cannot be returned to the file system.
Of course, you can shrink your database files. It is explained in note *363018* (points D and E). In fact, under certain circumstances it could be necessary to shrink your transaction log, as per note *625546* and note *421644*.
However, regarding your particular question, I would say that it could have a 'bad' effect: you would waste your resources or even hinder the performance during the time it takes the database shrinking and you wouldn't get a performance improvement in return. In fact, sooner or later your database will probably grow up to its current size or even more. Even more, as a rule of a thumb, it is recommended that each datafile has at least around 10-15% of free space.
At last, let me point out that you should not rely on SQL Server's "autogrow" function: this is recommended just to prevent the emergency situation that the database stops working because there is no free space left at all, but you are recommended to monitor and manually increase the datafiles whenever necessary.
You can also refer to the SAP Help Portal for further help on the +MS SQL Server DB administration in CCMS+ as well as on the +Database Management Tools+. You should always check the +Microsoft SQL Server 2005 *Books Online (BOL)*+
Cheers!!
-Jesú
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.