ACCESS 2007 DATABASE SIZE

Is there a database size limit for Access 2007 or is it determined by
storage space?

As far as I know, the size limit is 2 Gigs if you are using Jet or ACE as the
data repository. If you are using MS SQL server, then the limits are those
for your version of MS SQL server. If you are using Oracle or MySql or ...
then the size limits are governed by those applications.

However if you choose to split the data into multiple Access (Jet or ACE)
backends you can in theory have really large databases (up to 2 gigabytes for
each of the linked backends). I suspect that the performance could (probably
would) be terrible if you needed to do this.

John Spencer
Access MVP 2002-2005, 2007-2009
The Hilltop Institute
University of Maryland Baltimore County

Jim wrote:
Is there a database size limit for Access 2007 or is it determined by
storage space?

"John Spencer" wrote in message
...

However if you choose to split the data into multiple Access (Jet or ACE)
backends you can in theory have really large databases (up to 2 gigabytes
for each of the linked backends). I suspect that the performance could
(probably would) be terrible if you needed to do this.

Of course, you wouldn't be able to set relations between tables in different
backends.

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no private e-mails, please)

To clarify ..........

You would be able to set relationships between tables in a backend. You
wouldn't be able to set relationships between tables in different backends.

Steve



"Douglas J. Steele" wrote in message
...
"John Spencer" wrote in message
...

However if you choose to split the data into multiple Access (Jet or ACE)
backends you can in theory have really large databases (up to 2 gigabytes
for each of the linked backends). I suspect that the performance could
(probably would) be terrible if you needed to do this.

Of course, you wouldn't be able to set relations between tables in
different backends.

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no private e-mails, please)

And that's different than what I said how...?

You used the exact same words as me, Steve! "You wouldn't be able to set
relationships between tables in different backends."

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no private e-mails, please)


"Steve" wrote in message
...
To clarify ..........

You would be able to set relationships between tables in a backend. You
wouldn't be able to set relationships between tables in different
backends.

Steve



"Douglas J. Steele" wrote in message
...
"John Spencer" wrote in message
...

However if you choose to split the data into multiple Access (Jet or
ACE) backends you can in theory have really large databases (up to 2
gigabytes for each of the linked backends). I suspect that the
performance could (probably would) be terrible if you needed to do this.

Of course, you wouldn't be able to set relations between tables in
different backends.

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no private e-mails, please)

"John Spencer" wrote in message
...

However if you choose to split the data into multiple Access (Jet or ACE)
backends you can in theory have really large databases (up to 2 gigabytes
for each of the linked backends). I suspect that the performance could
(probably would) be terrible if you needed to do this.

Not as bad as one would think. In the huge 30 GB Access 2.0 database I once
worked on, a list box selection named the table, and a record could be
retrieved in a few seconds.

In an Access 2003 database with 2, 1+ GB backends, joined with a union
query. A record could be retrieved from over 12 million rows in about 20
seconds. Considering that it had to completely run the union query first,
that isn't too bad.
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com