I second Jochem. Just got back from giving a talk at OSCON on DataWarehousing with MySQL. MySQL is amazingly fast, and since data warehouses are full of read-only data (let's ignore the ETL step for a sec) then MySQL in many ways is a *far* better choice than MS-SQL or Oracle. The memory cache built into MySQL 4.0 (which you can manually set, and since MySQL runs on 64-bit platforms now, can put smaller datawarehouses completely in memory) plus the lack of transactional overhead for MyISAM tables is a clear win. Not to mention it's $XX,000 cheaper per processor than commercial solutions :)
That said, I'd rather load that data warehouse with data from an operational system that is running MS-SQL, Oracle, or PostgreSQL since those databases put a lot of effort into verifying the integrity of the data. I'm willing to take a performance hit for that in day-to-day operations because the tradeoff is worth it. When the OSS world finally has some decent CRM/ERP systems, I'm betting they run on PostgreSQL, not MySQL. That said, maybe Jochem or someone can shed some light -- do InnoDB tables have the same problem as the MyISAM tables for the reaction to bad data? In other words, is this a table handler issue (ie the MyISAM table handler is the culprit) or is it in the db engine itself? Regards, John Paul Ashenfelter CTO/TransitionPoint ----- Original Message ----- From: "Jochem van Dieten" <[EMAIL PROTECTED]> To: "CF-Talk" <[EMAIL PROTECTED]> Sent: Friday, August 01, 2003 5:49 AM Subject: Re: Access to MySQL Migration > Matt Robertson wrote: > > > > I've always thought of mySQL as an upscale Access that's the next > > logical step when your traffic overburdens the weak Access engine but > > your budget or needs aren't in league with a true grownup solution. > > This sort of malarkey reinforces that. > > I think MySQL is very different in nature from Access and it > should probably not be compared with any rdbms at all because of > its different nature. > With any rdbms I know, the focus is on the correctness of the > data and the vendors will sacrifice speed for that. With MySQL, > the focus is on speed, and the vendor will sacrifice correctness > of the data for that. > It is hard to overestimate the importance of that difference. > > Jochem > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. http://www.cfhosting.com Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
