Why DBMaker performance degraded after upgrading from 5.0.x to 5.2.x?
After upgrading from 5.0.x to 5.2.x without using unload/load method, only starting same DB files with the higher version modules, due to the system catalog’s differences between 5.0.x and 5.2.x, will face poor performance. To solve this problem, users need to execute “update statistics” to upgrade the entire system catalog.
Version: DBMaker 5.0.x/5.2.x
Product: Normal
Platform: Windows/Linux