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 assuming that you'll have connections to each database in your application. On Tue, 12 Oct 2004 17:43:11 -0700, Jason <[EMAIL PROTECTED]> wrote: > 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 into separate databases then cross-database joining the tables? > (these tables have anywhere between 1m and 5m+ rows) > > Thanks for any pointers in advance. If theres a major design flaw to > splitting a database up into separate databases I'd like to know before > getting to far down the path on this project :-) Thanks much for any > answers! > > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
