Overall Database size

[Surrealdogma]

I am looking at creating a database for my employer, are there any size
limitations for a table or for an overall file? Thanks in advance for your
help.

 

[Grover Park George]

The nominal maximum size for an Access db is 2 GB.

There are no specific limitations on the number of records in a field.

A properly designed database will have several (perhaps many) "Narrow"
tables related to one another.

 

[Grover Park George]

That should read "..number of records in a TABLE."

 

[Jeff Boyce]

As George points out, the more recent versions of Access have a 2 Gbyte
limit, but I suspect this is more theoretical than practical.

Also, a row has a maximum of 2K characters, from all fields combined.

The performance of an Access database will depend on a great many factors,
of which size is a less significant contributor.

--
Regards

Jeff Boyce
Microsoft Office/Access MVP


Microsoft IT Academy Program Mentor
http://microsoftitacademy.com/

Microsoft Registered Partner
https://partner.microsoft.com/

 

[Tom Wickerath]

Open Access Help and enter "Specifications" (without the quotes) to see a
listing of the various limits for your version of Access.


Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

 

[Surrealdogma]

Thank you!

 

[aaron.kempf]

I disagree.

a properly designed database should be rational... it doesn't need to
be narrow.

I proclaim that MS needs to start supporting VWDB = very wide database
in addition to VLDB.

I have worked against more than 100 tables with more than 100 fields
each.
It should be easier to do things like 'show me all of the fields in a
database in alphabetical order' in other words show the columns in
alphabetical order.

assholes that sit there and say 'every table must be narrow' dont
understand the practical measures-- the FACT that I have worked against
100 tables with 100 fields each.

anyone can sit there and preach THEORY.

Microsofts' products have a major shortcoming in that they don't
support VWDB.

not every field in your database needs to be a slowly changing
dimension
that is called 'unnecessary complexity'

what does a narrow table have to do with the price of beans in boston?

not every piece of data SHOULD be normalized

-Aaron