Compacting and repairing Microsoft Access database is necessary if one of the following scenarios are encountered:
- A GFI product backend Access database has grown very large.
- A GFI product backend Access database has been compromised or corrupted.
Currently, the GFI products do not perform the compact and repair of the databases automatically.
This article guides you on how to compact and repair the database through a command line and within Microsoft Access.
Compact and Repair from the Command Line
- If you have Microsoft Access installed on the same machine as your GFI product, you can process, compact, and repair from the command line.
- This can be easily inserted in a batch file which automatically stops the GFI services, and the IIS services; compact the database and restart the services stopped initially.
- The batch file can then be scheduled to run during the night, or when email flow is low for example.
- If Microsoft Access is not installed on the same machine as the GFI product, you can try using Jet Compact Utility.
- Open a command line and use the following command to perform compact and repair.
msaccess <path to database file>\<database file name> /compact
msaccess "C:\Program Files\GFI\MailEssentials\Data\Reports.mdb" /compact
- You can stop and start the required services using the
Identify the dependent services of the IIS Admin, so that you stop these before the IIS Admin and restart them after the IIS Admin starts.
Compact and Repair from Within Microsoft Access
- Take a backup copy of the .mdb file(s).
- After backing up the file, open each file in Microsoft Access.
- Go to Database Tools.
- Click Compact and Repair Database.
- Exit Microsoft Access.
NOTE: It is not recommended to let an MDB file exceed 1.7GB in size.
Scanresults.mdb Is Taking up Large Disk Space
Unable to Open GFI FaxMaker Configuration - The configuration files cannot be accessed.