General discussion


Database size

By mbonfyre ·
Could anybody advice me on the size capabilities of Databases (mainly Access and Oracle)?

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

capacity issues

by JimKunkel In reply to Database size

My experience with Access indicates that performance falls off with table size. We see degredations at binary 'milestones'; e.g., a noticeable change above 65536 records (64K) and a much more dramatic slowdown beyond 128K records. If your record count can be kept under 128K records per table, Access can be really convenient.

If you need to move to a more powerful db environment, think hard about the costs of Oracle and Micro$oft -- poor quality and expensive support and greater vulnerability to hackers.

We ported all our apps but one to postgreSQL and couldn't be happier. Great support from the community and a solid, easily administered system.

Collapse -


by cachitok In reply to capacity issues

Oracle is designed to support very very big table, if a table grows to much you can partition the table and their indexes in different tablespaces in different physical disks.
( but you'll need the Enterprise option )
It has too several ways to backup online big database, for backuping independently tablespaces.

Collapse -

by mbonfyre In reply to capacity issues

Many thanks, just the kind of information I needed

Collapse -

mr.vinny Bomm

by vinnyk27 In reply to Database size

i would like to do research in databases & information system's plz guide me how to write proposal's
thank u

Related Discussions

Related Forums