how_to:database_size
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| how_to:database_size [2017/04/26 11:07] – [Diagnostics logs] paul | how_to:database_size [2018/11/14 10:45] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 7: | Line 7: | ||
| * As with most database systems, when an entry is deleted, the free space is not returned to Windows, but is simply marked as free, and will be reused | * As with most database systems, when an entry is deleted, the free space is not returned to Windows, but is simply marked as free, and will be reused | ||
| - | A better way of seeing how much space is REALLY used by the data is to look at the size of the daily backups. Usually these will be much more stable in size. The backups do not contain the 'free space' or the database indexes. Depending on your settings, the backups may still grow, even if the amount of messages stays the same. This is because the data for the spam filter statistical analyser, historical logging, archived messages etc may still be increasing. | + | A better way of seeing how much space is REALLY used by the data is to look at the size of the daily backups. Usually these will be much more stable in size. The backups do not contain the 'free space' or the database indexes. Depending on your settings, the backups may still grow, even if the amount of messages stays the same. This is because the data for the spam filter statistical analyser, historical logging, archived messages etc may still be increasing. Note that the daily backups are usually compressed so will typically be about half the size of the uncompressed data. |
| =====Seeing where the data is being used===== | =====Seeing where the data is being used===== | ||
how_to/database_size.1493204831.txt.gz · Last modified: 2018/11/14 10:44 (external edit)
Page Tools
