Devart Forums

I am in the process of migrating from BDE to MySQL using myDAC. This first app is primarily executive reporting thru a data warehouse. Under BDE, all data was scraped and stored locally while being manipulated for reporting. Extremely FAST.
While changing over to MySQL and myDAC, I have had to change my LOCAL temporary tables to TEMPORARY MySQL tables on the server side. When using myTables to access these temporary tables to manipulate the data, performance is slower by 50x. Since these are working report tables only I do not need to reflect updates back to any main tables (which it looks like it may be trying to do) . I just want to fly thru and prep the data with whatever changes need to be made and send the results off to the report writer. I am doing something wrong or is there a setting on the myTable class I can set to get better performance. Sorry for being verbose but this is my first try with the migration and what I learn here will spread throughput the rest of my migration as well. Thanks in advance.

Bill

Performance loss when working with temporary tables on the MySQL server side in comparison to local temporary tables occurs due to the specificity of MySQL server functionality, and we can't affect this in any way.
You can learn how to increase performance in the MyDAC documentation: http://www.devart.com/mydac/docs/increa ... rmance.htm

Does temporary imply engine = memory?

davidmarcus wrote:Does temporary imply engine = memory?

See the information on this topic in the MySQL documentation: https://dev.mysql.com/doc/refman/5.1/en ... ables.html

That seems to be discussing internal temporary tables. Bill might try setting the engine to see if it makes a difference.

Thank you for being interested in our products.
If you have any questions during using our products, please don't hesitate to contact us - and we will try to help you solve them.