How to Handle the Microsoft Access 2 GB Database Limit
Question details
The user wants to know if it is possible to increase the maximum 2 GB size limit for Microsoft Access databases, as operations frequently fail on larger files in newer Office versions.

- Product
- Microsoft Access
- Device & OS
- not provided
- Scenario
- Hitting the 2 GB database limit or experiencing resource failures during large queries and database compaction.
- Observed behavior
- Newer Office versions fail to process large queries or compact the database due to the strict 2 GB size limit for ACCDB and MDB files, accompanied by system resource constraints.
Check your current Access database size by viewing the file properties in Windows File Explorer and identify the largest tables or queries that consume the most space before making any structural changes.
Split the Access Database into Front-End and Back-End
Since the 2 GB limit cannot be changed, splitting the database prevents you from hitting the limit by separating application objects from the data tables.
Microsoft Access provides a built-in Database Splitter wizard. This process creates a back-end database containing just your tables, while the front-end contains your queries, forms, and reports linked to those tables. This effectively doubles your available space.
Open your database in Microsoft Access, navigate to the Database Tools tab on the top ribbon, and click on Access Database located in the Move Data group.
Click the Split Database button in the dialog box that appears, and choose a network location or local folder to save the new back-end file.
Once the process completes, check the Navigation Pane in your front-end database to ensure your tables now show a small arrow icon, indicating they are successfully linked to the new back-end.

Migrate Access Data to SQL Server
For databases that continually grow past the 2 GB threshold, migrating the back-end data to SQL Server provides a scalable and robust solution.
Adjust Windows Virtual Memory Settings
If Access is failing during complex queries but the file size is still under 2 GB, increasing your system's virtual memory can resolve resource allocation errors.
Try WPS Office for a Lightweight Office Experience
While the Microsoft Access 2 GB limit cannot be increased and belongs to Microsoft's database architecture, managing complex office workflows requires a robust software environment. WPS Office offers a free, lightweight, and highly compatible alternative to Microsoft Office for your word processing, spreadsheet, and presentation needs, ensuring smooth performance without heavy system resource consumption.
- 1. Download WPS Office: Visit the official WPS website and download the free installation package for your operating system.
- 2. Install the software: Run the installer and follow the on-screen instructions to quickly set up WPS Office on your computer.
- 3. Open your files: Double-click your existing Microsoft Office documents to open and edit them effortlessly in WPS Writer, Spreadsheets, or Presentation.

Frequently Asked Questions
Why does Microsoft Access have a strict 2 GB limit?
The 2 GB limit is a hard-coded architectural restriction in the Access Jet/ACE database engine for both ACCDB and older MDB file formats. This limit encompasses all database objects, including tables, forms, reports, and system data.
Can adjusting Windows virtual memory bypass the Access size limit?
No. While increasing your system's virtual memory can help resolve "out of memory" errors during complex queries or heavy database operations, it will not increase the hard 2 GB file size limit of the Access database itself.
Does compacting and repairing the database help reduce its size?
Yes. Running the Compact and Repair tool in Access reclaims unused space left behind by deleted records and temporary objects. This can temporarily shrink the file size back down below the 2 GB threshold.
What should I do if my database frequently hits the 2 GB limit?
If you are consistently reaching the limit, you should permanently split your database into a front-end and back-end, archive older historical data, or migrate the back-end tables to a more robust platform like Microsoft SQL Server.




