Hi,
I found one thread on this that included some people's opinions, but I
haven't been able to find anyone who has actually done some performance
testing to see if there is a cost and what that cost is to doing cross
database joins. I do tend to want to keep everything in one DB
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
database on our server, and then a local
database on each machine. I have queries that have to be able to join
tables in the local and the server db's. I tried this with Interbase, and
it doesn't support cross-database joins. I'm wondering if MySql can do
this?
If so, how would you modify
on our server, and then a
local database
on each machine. I have queries that have to be able to join tables in the
local and the server db's. I tried this with Interbase, and it
doesn't support
cross-database joins. I'm wondering if MySql can do this?
If so, how would you modify
cross-database joins. I'm wondering if MySql can do this?
If so, how would you modify the below query to show the different databases?
Specifically, how would you specify the database that the table is in?
SELECT D.BkID, D.Chap, D.Vrs, D.RTypID
FROM :OntData:ScrpUF.DB D
INNER JOIN
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,