: Hello!
:
: I am faced with a database design dilemma. According to my
: most optimized design I would require a huge amount (1 million+)
: of tables. My question is: is it acceptable to have a large
: number of tables? And how well will the database handle this?
:
: Thank you VERY much in advance for your time.
:
: P.S. Please specify the database you are talking about. Thanks.
Could you please share with us *why* you need millions of tables?
This does not sound right at all. Millions of records in a table, or
in dozens or (in VERY extreme cases) one or two hundred tables, sounds
realistic, and well within the capabilities of desktop or
client/server database systems. But I've never seen a system with
more than a couple hundred tables, not because one couldn't be
designed, but because it's difficult to even conceive a situation
where you'd need any more than that.
Can you give us more details? Perhaps you do have a truly unique
situation; but more likely, what you're trying to do can be done more
efficiently through a smaler number of tables (each of which can have
as many records as the technology permits - up to about a few hundred
million in VFP, or as much as disk space permits in SQL Server).
Joe