[Melissa Siobhan]

How many of you who manage your database from the BMC choose the shrink database option. Up until now our database has not been "Shrunk". Do you recommend it? If yes, no, why?

Melissa

[Matthew]

yes - mainly just bc we're very space conscious

[RobertWild]

Yes, we've set it up as a weekly routine after the other database management stuff.

We do this to maintain smaller backup zip files, which we upload to our off-site server, in the event that the local server box is destroyed (surge/someone walking around with a REALLY BIG MAGNET!/other unforseen occurrance...)

[Melissa Siobhan]

We need to be more space conscious too which is why it is not set here.

Anyone else have an opinion?

[Harriet]

Quote:

Originally Posted by Melissa Siobhan

We need to be more space conscious too which is why it is not set here.

Anyone else have an opinion?

I do it here. I had a conversation with RE support when I first set up my backups and they advised the "shrink" option.

[SeanR]

I ensure of some routine shrink process. If using MS SQL a maintenance plan can be set to run as and when required.


Transaction log files can grow VERY large yet in some cases the large file is only "white" or empty space.
Yet it is actually alloted space on the disk.
If no and no shrink occurs you can run into disk space issues.
The shrink reduces the alloted file size to what the system requires for the actual contents not what was.

The file size grows based on your activity, until truncated, yet the system holds onto it just in case..a bit like keeping an RE 6 manual just in case..


Shrink, its a good thing..