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 ass
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 ther
Many thanks. You filled in the missing piece for me. It appears to be
working... at least with both databases on the same MySql server. I hope
that
putting one db on the file server and one locally does not prove to be
problematic (that issue never occurred to me), but if worse comes to worse,
Paul,
Ok. But that isn't what we are talking about.
If I understood him correctly, Dormition said he has one database on a remote
server and one on a local computer and thus they are NOT managed by the same
database "server":
> I have queries that have to be able to join tables in the
> local
It's perfectly possible to join tables from different databases, as long
as the databases are managed by the same server. Just qualify your
table names with a leading database name.
For example, a join between two tables in the same database might
be written like this:
SELECT t1.col1, t2.col2
F
You are talking about "heterogeneous queries". I believe it is Delphi which
achieves this feature for you, not the databases themselves. Here is a quote from
the Delphi help system:
"Delphi supports heterogeneous queries, that is, queries made against tables in
more than one database. A hete
