I'm actually using both at my company. I have a few FileMaker databases with over 100K records (Emails, Journal) with almost no performance issues. The largest databases increase by about 50-100 records a day. But I have one database with less than 20K records that was just getting too slow for complex full text searches in a large text field. MySQL takes about 2-3 seconds to do the same complex search that FileMaker did in about 20. There's also the problem of other FileMaker clients "pausing" while a search takes place. All of my test searches are actually faster in MySQL than in FileMaker.
About 6 months ago I decided I was going to switch everything over to PHP/MySQL. Mainly because I want a web front end and have never been impressed with Filemaker as a web backend. I've used CDML, Lasso and now fxPHP for my web front end to FileMaker. But FileMaker is just slow when accessed via the web.
The short answer is that yes, MySQL would speed things up if you do things right. MySQL is as scalable (compared to FileMaker) as FileMaker is easy to use. Two extremes. I wouldn't recommend using FileMaker as a front end to MySQL through a plug-in or ODBC.
On Apr 1, 2004, at 6:26 PM, Justin Tulloss wrote:
I am currently using FileMaker Pro for a relatively large database and I am
wondering how to speed it up. Would MySQL speed things up? Is FileMaker in
some way inferior to MySQL? If so, how? Would it be easy to use a FileMaker
plugin to access the MySQL database, or should I write a PHP front?
Thanks for you help,
Justin Tulloss Network Administrator InterChez Logistics Systems, Inc.
-- Brent Baisley Systems Architect Landover Associates, Inc. Search & Advisory Services for Advanced Technology Environments p: 212.759.6400/800.759.0577
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
