Converting MySQL Databases (MySQL to SQL)
After you have connected to MySQL, connected to SQL Server or SQL Azure, and set project and data mapping options, you can convert MySQL database objects to SQL Server or SQL Azure database objects.
Converting database objects takes the object definitions from MySQL, converts them to similar SQL Server or SQL Azure objects, and then loads this information into the SSMA metadata. It does not load the information into the instance of SQL Server. You can then view the objects and their properties by using the SQL Server or SQL Azure Metadata Explorer.
During the conversion, SSMA prints output messages to the Output pane and error messages to the Error List pane. Use the output and error information to determine whether you have to modify your MySQL databases or your conversion process to obtain the desired conversion results.
Before converting objects, review the project conversion options in the Project Settings dialog box. By using this dialog box, you can set how SSMA converts tables and indexes. For more information see, Project Settings (Conversion) (MySQL to SQL)
The following table shows which MySQL objects are converted, and the resulting SQL Server objects:
Resulting SQL Server Objects
Tables with dependent objects such as indexes
SSMA creates tables with dependent objects. Table is converted with all indexes and constraints. Indexes are converted into separate SQL Server objects.
Spatial data type mapping can be performed only at table node level.
For more information on the Table Conversion settings, see Conversion Settings
If the function can be directly converted to Transact-SQL, SSMA creates a function. In some cases, the function must be converted to a stored procedure. This can be done by using Function Conversion in Project Settings. In this case, SSMA creates a stored procedure and a function that calls the stored procedure.
For more information on Function Conversion settings, see Conversion Settings
If the procedure can be directly converted to Transact-SQL, SSMA creates a stored procedure. In some cases a stored procedure must be called in an autonomous transaction. In this case, SSMA creates two stored procedures: one that implements the procedure, and another that is used for calling the implementing stored procedure.
Databases as MySQL objects are not directly converted by SSMA for MySQL. MySQL databases are treated more like a schema names and all the physical parameters are lost during conversion. SSMA for MySQL uses Mapping MySQL Databases to SQL Server Schemas(MySQLToSQL) to map objects from MySQL database to appropriate SQL Server database/schema pair.
SSMA creates triggers based on the following rules:
SSMA creates views with dependent objects
To convert MySQL database objects, you first select the objects that you want to convert, and then have SSMA perform the conversion. To view output messages during the conversion, on the View menu, select Output.
To convert MySQL objects to SQL Server or SQL Azure syntax
In MySQL Metadata Explorer, expand the MySQL server, and then expand Databases.
Select objects to convert:
To convert all schemas, select the check box next to Databases.
To convert or omit a database, select the check box next to the Database name.
To convert or omit a category of objects, expand a schema, and then select or clear the check box next to the category.
To convert or omit individual objects, expand the category folder, and then select or clear the check box next to the object.
To convert all selected objects, right-click Databases and select Convert Schema.
You can also convert individual objects or categories of objects by right-clicking the object or its parent folder, and then selecting Convert Schema.
Some MySQL objects might not be converted. You can determine the conversion success rates by viewing the summary conversion report.
To view a summary report
In MySQL Metadata Explorer, select Databases.
In the right pane, select the Report tab.
This report shows the summary assessment report for all database objects that have been assessed or converted. You can also view a summary report for individual objects:
To view the report for an individual schema, select the database in MySQL Metadata Explorer.
To view the report for an individual object, select the object in MySQL Metadata Explorer. Objects that have conversion problems have a red error icon.
For objects that failed conversion, you can view the syntax that resulted in the conversion failure.
To view individual conversion problems
In MySQL Metadata Explorer, expand Databases.
Expand the database that shows a red error icon.
Under the database, expand a folder that has a red error icon.
Select the object that has a red error icon.
In the right pane, click the Report tab.
At the top of the Report tab is a drop-down list. If the list shows Statistics, change the selection to Source.
SSMA will display the source code and several buttons immediately above the code.
Click the Next Problem button. This is a red error icon with an arrow that points to the right.
SSMA will highlight the first problematic source code it finds in the current object.
For each item that could not be converted, you have to determine what you want to do with that object:
You can modify the object in the MySQL database to remove or revise problematic code. To load the updated code into SSMA, you will have to update the metadata. For more information, see Connecting to MySQL (MySQL to SQL)
You can exclude the object from migration. In SQL Server or SQL Azure Metadata Explorer and MySQL Metadata Explorer, clear the check box next to the item before loading the objects into SQL Server or SQL Azure and migrating data from MySQL.
The next step in the migration process is Loading Converted Database Objects into SQL Server (MySQLToSQL)