Find the benefits of Mysql _mysql

first step-install MySQL
Download this server, MySQL GUI tool, and MySQL ODBC driver to http://dev.mysql.com/downloads/. The servers you can choose from are: 5.0, 5.1 or 6.0. Then install them.
Considerations during the installation:
Your firewall should be set up to allow connection through 3306 ports.
Run MySQL as a service (you can choose the command-line method).
MySQL Install default username/login = root and server = localhost.
MySQL provides a choice of storage engine/table types-primarily Mysam and InnoDB. The latter looks more like access, it has transactions and foreign keys, so we use this approach in this article.
has user and security options. Don't forget to record all the passwords.
Also have to install bullzip access to MySQL and Dreamcoder for later use.
　 Step Two-move the table from access to MySQL
Use Bullzip to transfer the background datasheet to MySQL, or open your database and export your data through ODBC.
Things to be aware of:
MySQL does not recognize the functions that access defaults to fields (for example, the now () and date () functions in the Date/time field): They may be deleted or the table will be rejected. It is recommended that you delete them before transfer/export.
Access's AutoNumber field is inconsistent with the MySQL auto_increment field. Bullzip is converted when it is transferred, while ODBC does not.
The Access data type is converted to a similar MySQL data type. However, in MySQL the scope is bigger, you may want to change them later.
Access's "OLE Object" becomes a "blob" in MySQL. Because of an OLE server problem, we change the blobs to Longtext.
Step Three--change the MySQL table (field)
Open the Dreamcoder or MySQL manager (a GUI tool). If you are familiar with SQL Server, consider these as enterprise or SQL Server Management Studio Express interfaces.
Connect to this transfer/export database.
Open each table sequentially and check:
The AutoNumber field is auto_increment.
Each table has a primary key (one or more fields) (in Dreamcoder, create-new constraint). Otherwise, you need to specify the connection, otherwise the linked table will not be updated.
The field is correct by default. We check the consistency of the login defaults with the front-end data.
Whether null values are allowed.
Whether the data type is as expected.
There is a timestamp field, which defaults to Current_time (typically the last field in the table).
step Four--build your MySQL backup system
Open the MySQL manager and back up your MySQL database. This saves the schema and data to a. sql file. If you want to build a database on another computer, install a MySQL server on that machine, and then restore a copy of this. sql file to the new server.
Step Five--from the front-end chain to MySQL
Open the front of your access. If you've already linked to an access background, you can't use the linked Table Manager to change to an ODBC data source. So delete the links to the background of access and link to MySQL backstage via ODBC. Similarly, once you have linked to an ODBC data source, this linked Table Manager provides only the options for ODBC data sources.
When you set up an ODBC data source,--ADVANCED--FLAGS1 in the ODBC configuration, check return Matching rows and allow big Results.
Performance
To the present observation:
Access 97 with a MySQL background is significantly faster than Access 2007 using the same background.
Initially this mixed and list record source uses the record source query Builder. For some reason, a significant increase in speed can be achieved by replacing them with queries created by users.
In today's configuration, Access 2007 is faster than using MySQL backstage.