PROBLEM
The size of a personal geodatabase does not change after removing features and feature classes
Description
When editing a personal geodatabase and deleting features or when feature classes and tables are deleted from a personal geodatabase using ArcCatalog, the size of the MDB file may not change.
Cause
Personal geodatabases are stored and managed in Microsoft Access data files (MDB files). As data is added and edited within a personal geodatabase, the MDB file increases in size to accommodate the data and may become fragmented on a disk. The MDB file does not decrease in size when data is removed; space allotted for the data continues to be held in reserve by the MDB file.
Solution or Workaround
Use the Compact Database command in ArcCatalog to compact the personal geodatabase. Compact rearranges how a fragmented personal geodatabase is stored on disk. Compacting a personal geodatabase often reduces its size and improves performance.
See the following ArcGIS Desktop help topic for more information on compacting a personal geodatabase:
Compacting a personal geodatabase.
Article ID: 000003078
- ArcMap
Receive notifications and find solutions for new or common issues
Get summarized answers and video solutions from our new AI chatbot.
Discover more on this topic
Search for related information
Find training related to this topic
Explore ideas and give feedback
Get help from ArcGIS experts
Download the Esri Support App