OK, probably the wrong section, so sorry if it is...
We have been playing around with external reporting tools using the progress ODBC drivers, and came across one bit of software that would only connect to MySQL. So we dumped a stats table and loaded it into MySQL, and did some analysis.
We connected to the MySQL database, and found that results were coming back rather fast. After checking that we had actually loaded all the data, we were a little confused.
We found FlySpeed SQL Query, and connected to both the MySQL and Progress databases via ODBC, and ran some queries. We then ran the same query back at the Progress Procedure editor.
Then, we wondered why we use Progress at all, as the un-indexed table on the "out-of-the-box" configuration of MySQL was about 2-3 times faster than an indexed table running as a tuned Progress service.
I found this http://www.progresstalk.com/showthread.php?t=112541 and wondered about indexs, so created a new database, dumped and reloaded the data with no indexes, just to see what happened. It was much slower as you would expect, so that didn't work.
I contacted Progress tech support to ask what the difference was, and they just batted it off to their consultancy service for database tuning, saying that this wasn't in the scope of tech support.
Does anyone have any ideas why a tuned commercial product like progress is so ludicrously slower than a free, open-source, "out-of-the-box" product like MySQL?
We have been playing around with external reporting tools using the progress ODBC drivers, and came across one bit of software that would only connect to MySQL. So we dumped a stats table and loaded it into MySQL, and did some analysis.
We connected to the MySQL database, and found that results were coming back rather fast. After checking that we had actually loaded all the data, we were a little confused.
We found FlySpeed SQL Query, and connected to both the MySQL and Progress databases via ODBC, and ran some queries. We then ran the same query back at the Progress Procedure editor.
Then, we wondered why we use Progress at all, as the un-indexed table on the "out-of-the-box" configuration of MySQL was about 2-3 times faster than an indexed table running as a tuned Progress service.
I found this http://www.progresstalk.com/showthread.php?t=112541 and wondered about indexs, so created a new database, dumped and reloaded the data with no indexes, just to see what happened. It was much slower as you would expect, so that didn't work.
I contacted Progress tech support to ask what the difference was, and they just batted it off to their consultancy service for database tuning, saying that this wasn't in the scope of tech support.
Does anyone have any ideas why a tuned commercial product like progress is so ludicrously slower than a free, open-source, "out-of-the-box" product like MySQL?