Jesper B. Kiær wrote:

>Hi
>
>Thanks for the quick reponse :-)
>
>My question on designing the database "the right way" is not so much the
>application I'm working on but more in a generelle sense...like when is a
>certain amount af tables considered "too many" design wise?
>
>I plan to use Firebird a lot in the future, so would really like to do it
>"the right way"
>
>I come from a Lotus Notes/Domino world where it is normal to split data
>into different databases
>
>Not being able to do cross database joins, I guess forces one to use a
>single database pr. application ?
>
>
>regards
>Jesper B. Kiær
>
>Jezzper Consulting
>Website : http://www.jezzper.com
>
>
>

Jesper,

Firebird has a limit of 64k tables, wich is a big number of tables :-)

You should not notice performance problems related to the number of
tables in you database.

The performance could degrade if you have transactions open for long
periods, if you do join on large tables and teh indexes are not adequated.

On FB 1.5 you cannot make cross database joins, in future versions
proably you will can...

I think you should experiment, and when you think something is slow post
here with a good description, and some information about your
enviroment, and certainly the masters (I don't belong to the masters
group, they are almost all in Fulda/Germany on 2nd Firebird conference)
will find a solution.


See you !