In article [EMAIL PROTECTED],
Jason [EMAIL PROTECTED] writes:
I've tried to find references to if there are any design flaws with using
multiple databases or not however was unable to locate anything (but I was
told by a previous co-worker that there were performance hits).
Are there any
I've worked on projects before where splitting up the schema into
databases was used. Joins across DB's are fine, but there is another
place that the performance can hit you.
If you use something like perl's Apache::DBI, you will increase the
number of open connections to your database. That's
I've tried to find references to if there are any design flaws with using
multiple databases or not however was unable to locate anything (but I was
told by a previous co-worker that there were performance hits).
Are there any performance hits or design flaws by separating a large
database
