When purging the entity repository database on SQLite, although the data is removed the physical disk space remains in use and allocated. Consider the following example.
After loading the default SQLite database - G2C.db - has a size of 89M. Using G2Command we can purge the entity repository by calling the purgeRepository API.
After purging the repository, the G2C.db file is still using 89M! SQLite leaves behind the free database pages. If you are attempting to reclaim a large volume of space and wish to reclaim the free space the G2C.db file is holding you can perform one of the following procedures:
- SQLite VACUUM command
- Replace the G2C.db file with the Senzing default
Copy the default G2C.db from the /opt/senzing/data directory to replace the one in /opt/senzing/sqldb