Support
[ Home ] [ MySQL2Access ] [ Access2MySql ] [ Download ] [ Order ] [ Data mapping ] [ Support ] [ Similar products ]

Support

For any inquiry, please write to support@fonlow.com

Please visit www.fonlow.com/dbconverters  for latest info.

 

Troubleshooting

Q: When I copy Access tables to MySql databases, an error message appeared "SQL Err: Get a packet bigger than "max_allowed_packet".

A: You might have big OLE object in your Access tables. Please increase the value of variable "max_allowed_packet" of MySql to 8M, 16M or 32M or even bigger. There are a few ways to modify the variable. If your MySql server is running on a Windows machine, you may modify "my.ini" in Windows' system folder like "system32". You might need to restart MySql server.

General hints for data migration

In the following cases, you may need to use a data migration tool to migrate databases from one engine to another:

  1. To develop a series of products, one edition for a Sql server, and the other edition for the other database engine.
  2. To upgrade database applications, using new database platform.
  3. To export data from one information system, and import data to other information systems.

In case one, when you design the database, you should use only those data types common in both platforms, so you can easily have one set of source codes to support both editions for two database platforms.

In case two, even if you are going to abandon the old database platform and use advance features of the new platform, it might be safer to take the following steps if you want to reuse the source codes of the applications:

  1. Modify existing database structures, use only those data types common in existing platform and the future platform. Upgrade the applications to adapt the new database structures. This upgraded version is to prepare for major upgrade jobs following.
  2. Run the applications for a period in order to make sure things are OK.
  3. Export the database from existing database platform to the new one. Upgrade the applications to connect with the new database platform.
  4. Run the upgraded applications with the new database platform for a period.
  5. Upgrade the databases using advanced features of the new platform.

This approach may give you safety nets for your system upgrades as a whole, make your life easier respecting to deployment and debugging.

Please find more info about dealing with legacy applications at the following links:

http://www.agiledata.org