Re: Advise Please on big EDB
Tony Steward writes:
> I have 2700 lists of data, each list containing
> between 200 and 10,000 items.
Everything in EDS is flexible.
The only hard limit arises from internal
pointers within a database being 32 bits.
That means a single database file can't
exceed 4Gb (although some future enhancement
to EDS could move to 64 bits without breaking any code).
> The question is do I create 1 database with 2700 tables?
I don't know what the data is, or how you will typically
access it. You could have 2700 tables,
or you could have 2700 records in one table,
with from 200 to 10,000 items stored in each record
(record-size is very flexible). Anything is possible.
> Can EDB handle this many tables?
Yes.
> Would it be faster to access the data if each
> table was in fact an individual file?
I've never noticed a speed difference between
reading/writing a large file vs. reading/writing a small file,
but there would be some extra overhead from
*opening and closing* many small files
vs opening a single large file.
> Any tips on handling data of this size?
Make sure you keep backups.
Even if the software is perfectly-coded (big assumption),
you never know when a power failure or disk failure
might occur. If the database gets corrupted, you'll
have to roll it back to a previous good state
Regards,
Rob Craig
Rapid Deployment Software
http://www.RapidEuphoria.com
|
Not Categorized, Please Help
|
|
