Upsize to MySQL

You upsize your model repository to a MySQL database in the following stages:

Stage One: Install MySQL Components

  1. Install MySQL version 4.0.3 or higher.
  2. Install MySQL ODBC 3.51 or higher.
  3. Create a suitable ODBC Data Source to point to your new database.


There are two critical non-default settings required; see the Set up a MySQL ODBC Driver topic and ensure you select the checkboxes as directed in step 7 of that procedure.

Stage Two: Select Table Type

  1. If you are using InnoDB tables, set up the MySQL .ini file as required and run the MySQL_InnoDB_EASchema.sql script.
  2. If you are using MyISAM tables, set up the MySQL .ini file as required and run the MySQL_MyISAM_EASchema.sql script.


If MyISAM table types are used (default), transactional support is disabled. To enable transactions you must set up MySQL to use InnoDB tables and create the database tables as InnoDB type. Sparx Systems provides a suitable script to create InnoDB based repository tables, as well as the more common MyISAM. These are available from the Sparx Systems website.

Stage Three: Create the Repository

  1. Create an empty repository.

You now can transfer an existing model into the MySQL repository as described below.

Stage Four: Perform Integrity Check

Run the project integrity check tool (select the Tools | Data Management | Project Integrity Check menu option) on the base project that you intend to upsize to the MySQL repository, to ensure the project data is 'clean' before uploading.

Stage Five: Transfer the Data

  1. Open Enterprise Architect and select the Tools | Data Management | Project Transfer menu option. The Project Transfer dialog displays.
  2. In the Transfer Type panel, select the .EAP to DBMS radio button.
  3. In the Source Project field, type the name of the .EAP file to upsize to MySQL.
  4. At the right of the Target Project field, click on the [ ... ] (Browse) button. The Data Link Properties dialog displays, showing the Provider tab.
  5. Select Microsoft OLE DB Provider for ODBC Drivers from the list, then click on the Next>> button. The Connection tab displays.
  6. Click on the Use data source name radio button and on the drop-down arrow, and select the ODBC Data Source you configured to point to your new database. In the setup example the driver title is Changes.
  7. If required, type a User name and Password.
  8. If required, in the Enter an initial catalog to use field type an initial catalog.
  9. Click on the Test Connection button to confirm that the details are correct.
  10. If the test does not succeed, revise your settings. If the test succeeds, click on the OK button. The Project Transfer dialog redisplays.
  11. If required, select the Logfile checkbox and type a path and filename for the data transfer log file.
  12. Click on the Transfer button to begin the data transfer process.

Once this process is complete, the content of the .EAP model exists on the MySQL repository and you can now open the repository from Enterprise Architect.


You cannot transfer a source .EAP file that was created using a version of Enterprise Architect earlier than 3.5.0.