Amazon RDS For MySQL
Amazon RDS For MySQL
Executive summary
We completed the analysis of your Microsoft SQL Server source database and estimate that 100% of the
database storage objects and 84% of database code objects can be converted automatically or with minimal
changes if you select Amazon RDS for MySQL as your migration target. Database storage objects include
schemas, tables, table constraints, indexes, types, table types, sequences, synonyms and xml schema collections.
Database code objects include triggers, views, procedures, scalar functions, inline functions, table-valued
functions and database triggers. Based on the source code syntax analysis, we estimate 97% (based on # lines of
code) of your code can be converted to Amazon RDS for MySQL automatically. To complete the migration, we
recommend 996 conversion action(s) ranging from simple tasks to medium-complexity actions to complex
conversion actions.
Migration guidance for database objects that could not be converted automatically can be found here
Schema
1
(1: 1/0/0/0)
Table
100% 146
(146: 146/0/0/0)
Constraint
100% 142
(142: 142/0/0/0)
Index
67% 33% 3
(3: 2/1/0/0)
0 10 100 1000
Procedure
56% 27% 9% 7% 365
(365: 205/100/33/27)
Scalar function
71% 29% 7
(7: 5/2/0/0)
Table-valued function
100% 2
(2: 0/2/0/0)
0 10 100 1000
Index Changes
Not all indexs can be converted automatically. You'll need to address these issues manually.
Procedure Changes
Not all procedures can be converted automatically. You'll need to address these issues manually.
Issue 659: The scope table-variables and temporary tables is different. You must apply
Issue 675: These keywords are reserved for future extensions to specify ascending or
descending index-value storage. Currently, these keywords are parsed but ignored. Index
values are always stored in ascending order
Recommended action: Use indexes without this option.
Issue code: 675 | Number of occurrences: 2 | Estimated complexity: Simple
Documentation references: http://dev.mysql.com/doc/refman/5.7/en/create-index.html
Databases.ADIDAS.Schemas.dbo.Procedures.sp_upgraddiagrams: 394:405
Databases.ADIDAS.Schemas.dbo.Procedures.sp_upgraddiagrams: 413:416
Issue 696: MySQL doesn't support an Identity column with seed and increment
Recommended action: Perform a manual conversion.
Issue code: 696 | Number of occurrences: 1 | Estimated complexity: Simple
Databases.ADIDAS.Schemas.dbo.Procedures.SetCargaMasivaFile: 832:844
Issue 697: MySQL doesn't support an Identity column outside a primary key
Recommended action: Perform a manual conversion.
Issue code: 697 | Number of occurrences: 4 | Estimated complexity: Simple
Databases.ADIDAS.Schemas.dbo.Procedures.B2B_TraeRankingCacs_Tx: 671:678
Databases.ADIDAS.Schemas.dbo.Procedures.ConsultaProductosPremiacion_Tx: 1860:1867
Databases.ADIDAS.Schemas.dbo.Procedures.ConsultaProductosPremiacion_Tx: 2724:2731
Databases.ADIDAS.Schemas.dbo.Procedures.SetCargaMasivaFile: 832:844
Issue 774: Unable to perform an automated migration of the arithmetic operations with
mixed types of operands
Recommended action: Make cast operands to the expected type.
Issue code: 774 | Number of occurrences: 22 | Estimated complexity: Simple
Databases.ADIDAS.Schemas.dbo.Procedures.B2B_InsertaReglas: 525:545
Databases.ADIDAS.Schemas.dbo.Procedures.B2B_InsertaReglas: 568:585
Databases.ADIDAS.Schemas.dbo.Procedures.B2B_RptFacturas: 1440:1460
Databases.ADIDAS.Schemas.dbo.Procedures.B2B_RptFacturas: 1466:1483
Databases.ADIDAS.Schemas.dbo.Procedures.B2B_RptSociosRegistrados: 4229:4249
+17 more
Issue 905: MySQL doesn't support the PIVOT clause for the SELECT statement
Recommended action: You can use a stored procedure to prepare data, and then return the data with a VIEW.
Issue code: 905 | Number of occurrences: 8 | Estimated complexity: Simple
Documentation references: https://dev.mysql.com/doc/refman/5.7/en/create-view.html
Databases.ADIDAS.Schemas.dbo.Procedures.B2B_RptSociosRegistrados: 2782:2868
Databases.ADIDAS.Schemas.dbo.Procedures.B2B_RptSociosRegistrados: 3121:3176
Databases.ADIDAS.Schemas.dbo.Procedures.B2B_RptSociosRegistradosGrid: 2088:2174
Databases.ADIDAS.Schemas.dbo.Procedures.B2B_RptSociosRegistradosGrid: 2427:2482
Databases.ADIDAS.Schemas.dbo.Procedures.ReporteFacturacionActualizado150: 1421:1577
+3 more
Issue 731: MySQL doesn't support this construction. A manual conversion is required
Recommended action: Try converting the WITH(query) expression to a subquery and use it in a SELECT query.
Issue code: 731 | Number of occurrences: 1 | Estimated complexity: Complex
Databases.ADIDAS.Schemas.dbo.Procedures.RPT_Intranet_Weekly: 1369:1700
Not all table-valued functions can be converted automatically. You'll need to address these issues manually.
Issue 696: MySQL doesn't support an Identity column with seed and increment
Recommended action: Perform a manual conversion.
Issue code: 696 | Number of occurrences: 2 | Estimated complexity: Simple
Databases.ADIDAS.Schemas.dbo.SQL table-valued functions.B2B_split_to_table_Canje: 473:486
Databases.ADIDAS.Schemas.dbo.SQL table-valued functions.split_to_table: 509:522
Issue 697: MySQL doesn't support an Identity column outside a primary key
Recommended action: Perform a manual conversion.
Issue code: 697 | Number of occurrences: 2 | Estimated complexity: Simple
Databases.ADIDAS.Schemas.dbo.SQL table-valued functions.B2B_split_to_table_Canje: 473:486
Databases.ADIDAS.Schemas.dbo.SQL table-valued functions.split_to_table: 509:522