MS-Access Maximum Database Size and Performance

Article View: comp.databases.ms-access

Article #381

Back to comp.databases.ms-access Previous Next

#381

From: NinkSink
Date: Wed, 29 Jul 1998 00:00

42 lines
3027 bytes

Hello all.  A few questions about MS-Access '97 on a Pentium

Does anyone know a ball-park figure of the max size an MS-Access '97 database can become
before MS-Access applications have performance and/or data integrity faults.  I would also

like to know the maximum # of records (I know this could be subjective in that record size

can be an issue too, so for arguements sake, figure on a record that is roughly 1000 bytes

in length) that can be in a MS-Access table before query (for arguements sake say the
table has one index on a long integer field) performance is hindered.  Also for arguements

sake, figure the PC has 16-32Mb of RAM and is a Pentium 133 or better.

I have looked in MS-Access Help, which states the maximum Access database size is 1Gig,
but I have a feeling that performance will be subject to slowness long before the database

reaches that size.

I vaguely remember hearing that Access 2.0 would have query and update problems with
tables > 100,000 records, so I am wondering if Access 97 may have the same potential
restrictions regardless if it is now 32 bit and fancier.

--
http://www.army-technology.com/projects/merkava/images/merkava5.jpg
http://www.army-technology.com/projects/merkava/images/merkava4.jpg
http://www.army-technology.com/projects/challenger2/images/chal6.jpg
http://www.army-technology.com/projects/challenger2/images/chal1.jpg
http://www.isrv.com/~falon/m1fk.gif
http://www.army-technology.com/projects/abrams/images/abram7.jpg
http://www.army-technology.com/projects/leopard/images/leop2.jpg
http://www.army-technology.com/projects/leopard/images/leop9.jpg
http://www.army-technology.com/projects/t90/images/t90_1.jpg
http://www.army-technology.com/projects/t90/images/t90_5.jpg
http://www.army-technology.com/projects/t90/images/t90_3.jpg
http://www.army-technology.com/projects/leclerc/images/leclerc3.jpg
http://www.army-technology.com/projects/leclerc/images/leclerc1.jpg
http://www.army-technology.com/projects/himars/images/himars4.jpg
http://www.army-technology.com/projects/mlrs/images/mlrs1.jpg
http://www.army-technology.com/projects/mlrs/images/mlrs8.jpg
http://www.army-technology.com/projects/ka50/images/ka50_6.jpg
http://www.army-technology.com/projects/comanche/images/comanche1.jpg

Technical Details

Message-ID: <35BFC453.3C37EE36@earthlink.net>

Path: arc1-ca.pugleaf.net!unknown!not-for-mail

Show Full Headers

Complete Article Headers

X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 111a5a,a794ac29ee401323,start
X-Google-Attributes: gid111a5a,public
X-Google-Thread: ff0ac,a794ac29ee401323,start
X-Google-Attributes: gidff0ac,public
X-Google-Thread: f8db2,a794ac29ee401323,start
X-Google-Attributes: gidf8db2,public
From: NinkSink <nutropetfood@earthlink.net>
Subject: MS-Access Maximum Database Size and Performance
Date: 1998/07/29
Message-ID: <35BFC453.3C37EE36@earthlink.net>
X-Deja-AN: 376180419
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii
Organization: Whatever
Mime-Version: 1.0
Reply-To: nutropetfood@earthlink.net
Newsgroups: comp.databases.ms-access,es.comp.bd.ms-access,it.comp.database.access