


END block like one in procedure, function or trigger definition. END block conversion, the SQL statement can also contain a BEGIN.

Each SQL statement object may contain a single MySQL statement (like DDL, DML, and other types of statements) or BEGIN. SSMA creates views with dependent objects AFTER triggers are converted into AFTER T-SQL triggers with or without iterations per rows. BEFORE triggers are converted into INSTEAD OF T-SQL triggers SSMA creates triggers based on the following rules: 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. MySQL databases are treated more like a schema name and all the physical parameters are lost during conversion. In this case, SSMA creates two stored procedures: one that implements the procedure, and another that is used for calling the implementing stored procedure.ĭatabases as MySQL objects are not directly converted by SSMA for MySQL. In some cases a stored procedure must be called in an autonomous transaction. If the procedure can be directly converted to Transact-SQL, SSMA creates a stored procedure. In this case, SSMA creates a stored procedure and a function that calls the stored procedure.įor more information on Function Conversion settings, see Conversion Settings This can be done by using Function Conversion in Project Settings. In some cases, the function must be converted to a stored procedure. If the function can be directly converted to Transact-SQL, SSMA creates a function. Spatial data type mapping can be performed only at table node level.įor more information on the Table Conversion settings, see Conversion Settings Indexes are converted into separate SQL Server objects. Table is converted with all indexes and constraints. SSMA creates tables with dependent objects. Tables with dependent objects such as indexes The following table shows which MySQL objects are converted, and the resulting SQL Server objects: MySQL Objects For more information, see Project Settings (Conversion) (MySQLToSQL). By using this dialog box, you can set how SSMA converts tables and indexes. Set conversion optionsīefore converting objects, review the project conversion options in the Project Settings dialog box. 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. You can then view the objects and their properties by using the SQL Server or SQL Azure Metadata Explorer.ĭuring the conversion, SSMA prints output messages to the Output pane and error messages to the Error List pane. It doesn't load the information into the instance of SQL Server. The conversion processĬonverting database objects takes the object definitions from MySQL, converts them to similar SQL Server or Azure SQL objects, and then loads this information into the SSMA metadata.

After you have connected to MySQL, connected to SQL Server or Azure SQL, and set project and data mapping options, you can convert MySQL database objects to SQL Server or Azure SQL Database objects.
