How many rows of data will an access database table hold?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

How many rows of data will an access database table accept? I was told around
2G, but I need a row count. If not an exact count an approx.
 
It depends upon the average size of each record/row. Jet
(the actual database engine that Access uses) will keep
creating rows until the mdb file containing the table(s)
gets to around 2GB. You can cheat by spreading your tables
out over a number of data mdb files (also called Back Ends).

If you need more than that then you should consider using
Access as the front end to a SQLServer or Oracle or PostGres
or whatever database Back End.

It's really a limitation of ISAM type database engines
rather than Access.

--
Nick Coe (UK)
http://www.alphacos.co.uk/ AccHelp + pAnimal
http://www.pjandcoe.co.uk/ Online Store
http://www.mrcomputersltd.com/ Repairs Upgrades

In Tonya typed:
 
How many rows of data will an access database table accept? I was told around
2G, but I need a row count. If not an exact count an approx.

Access 2000 and newer has a total database size of 2 gigabytes (not
rows).
That includes the code, forms, reports, etc. as well as the data.

See Access help.
Specification + Access Specifications + Access database
 
As others have said, there is no specific row limit. You can probably arrive
at a rough approximation, though.

I'm assuming that your data is split from your application, i.e. you have a
'back-end' data MDB containing nothing but tables and a 'front-end'
application MDB with forms, reports etc. and links to those tables - that
is, if the application is an Access application at all. Compact this
data-only MDB, then create a new database containing empty copies of the
tables in the original database. To do this, import the tables from the
original database, but in the Import Objects dialog box choose 'Options' and
then choose the option 'Definition Only'.

The size of this new database is, approximately, the 'overhead' of your
database and table definitions. The difference between the size of this new
database and the size of your old database is, approximately, the space
taken up by your records and associated indexes. Divide that by the number
of records to get, approximately, the average size of a record in your
database. Divide 2GB minus the above mentioned overhead by your average
record size to get, approximately, the number of records you can fit into
2GB.

The key word in all of the above, of course, is 'approximately'.

There are factors that could make this approximation more or less ... um ...
approximate. For example, the average arrived at will be an overall average
of all records in all tables. You might have some tables with very small
records and other tables with very large records. If you expect to add lots
of records to one of these tables, but far fewer records to the other, you'd
need to adjust your estimate accordingly.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top