<snip> However, if you're going to be doing massive joins for reporting, you're better off using something else (or running individual MySQL slaves, whose purpose is to run those complex queries and doing nothing else). In a past life, our MySQL database ran circles around Oracle, Informix, and DB2... until someone ran a massive join on the same server, which caused MySQL to crawl. </snip>
Good distinction to make. I should have been more clear. I believe mysql has read only slave capabilities within a clustered environment, so your point about the slaves isn't out of the question. However I don't believe in database engines doing really anything other than transaction processing. That's why IMHO there should always be a distinction between the database backend and whatever software you're using to generate OLAP data (this software should NOT be the database engine). I know this is not a common opinion, but if we keep the database engine doing what it's good at and leave any report processing to external software, we're generally able to get better performance out of each individual piece... -Dave -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
