Amazon Aurora (MySQL Compatible)

Database migration assessment report
Source database:
Eadpi.dbo.root@sqlserver2012ee.c1sleazgkfyg.eu-west-1.rds.amazonaws.com\sqlserver2012ee.c1sleazgk
fyg.eu-west-1.rds.amazonaws.com:1433
Microsoft SQL Server 2012 (SP4-GDR) (KB4532098) - 11.0.7493.4 (X64) Dec 24 2019 19:33:24
Copyright (c) Microsoft Corporation
Enterprise Edition: Core-based Licensing (64-bit) on Windows NT 6.3 <X64> (Build 14393: ) (Hypervisor)
Case sensitivity: OFF
Warning
We found that your source database may be configured not in correct way or you have not enough privileges for
reading all necessary metadata. Please check your configuration and run report again. For more details please
review help documentation.
List of Action Items to review:
1. Unable to resolve objects - 313 occurrences
Executive summary
We completed the analysis of your Microsoft SQL Server source database and estimate that 100% of the
database storage objects and 44% of database code objects can be converted automatically or with minimal
changes if you select Amazon Aurora (MySQL compatible) 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 96%
(based on # lines of code) of your code can be converted to Amazon Aurora (MySQL compatible) automatically.
To complete the migration, we recommend 470 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
Database objects with conversion actions for Amazon Aurora

(MySQL compatible)
Of the total 27 database storage object(s) and 32 database code object(s) in the source database, we identifed
27 (100%) database storage object(s) and 14 (44%) database code object(s) that can be converted to Amazon
Aurora (MySQL compatible) automatically or with minimal changes.
18 (56%) database code object(s) require 1 medium and 22 complex user action(s) to complete the conversion.
Figure: Conversion statistics for database storage objects
Schema
1
(1: 1/0/0/0)
Table
36% 64% 11
(11: 4/7/0/0)
Constraint
100% 10
(10: 10/0/0/0)
Index
60% 40% 5
(5: 3/2/0/0)
0 10 100
Objects automatically converted Objects with simple actions

Objects with medium-complexity actions Objects with complex actions
AWS Schema Conversion Tool Version 1.0.644 Page 1 of 6

01/27/2021 9:39AM
Source database:
Figure: Conversion statistics for database code objects
Procedure
29% 16% 55% 31
(31: 9/5/0/17)
Table-valued function
1
(1: 0/0/0/1)
0 10 100
Objects automatically converted Objects with simple actions

Objects with medium-complexity actions Objects with complex actions
Detailed recommendations for Amazon Aurora (MySQL compatible)

migrations
If you migrate your Microsoft SQL Server database to Amazon Aurora (MySQL compatible), we recommend the
following actions.
Storage object actions
Table Changes
Not all tables can be converted automatically. You'll need to address these issues manually.
Issue 677: MySQL doesn't support using a function or expressions as a default value and
default value for BLOB/TEXT columns. It is emulated by trigger
Recommended action: Please review generated code and modify it if necessary.
Issue code: 677 | Number of occurrences: 7 | Estimated complexity: Simple
Databases.Eadpi.Schemas.dbo.Tables.Delivery_Header.Columns.CreatedAt
Databases.Eadpi.Schemas.dbo.Tables.Delivery_Items.Columns.CreatedAt
Databases.Eadpi.Schemas.dbo.Tables.Log.Columns.CreatedAt
Databases.Eadpi.Schemas.dbo.Tables.MasterData_MaterialGroups.Columns.ChangedAt
Databases.Eadpi.Schemas.dbo.Tables.MasterData_ShipToParty.Columns.ChangedAt
+2 more
Index Changes
Not all indexs can be converted automatically. You'll need to address these issues manually.
Issue 681: MySQL doesn't support creating indexes with a CLUSTER option. The user can't
create CLUSTER INDEX, MySQL will create it automatically
01/27/2021 9:39AM
Source database:
Recommended action: Use non-clustered indexes.

Databases.Eadpi.Schemas.dbo.Tables.MasterData_Conditions.Indexes.IX_MasterData_Conditions
Databases.Eadpi.Schemas.dbo.Tables.MasterData_ShipToParty.Indexes.IX_MasterData_ShipToParty
Code object actions
Procedure Changes
Not all procedures can be converted automatically. You'll need to address these issues manually.
Issue 646: MySQL doesn't support the COLLATE option. Automatic conversion ignores this
clause
Recommended action: You must use the COLLATION settings that were assigned when the database was
created.
Documentation references: https://dev.mysql.com/doc/refman/5.7/en/select.html
Databases.Eadpi.Schemas.dbo.Procedures.GET_MasterData_FA_SpecialCases_Warning
+25 more
Issue 663: Unable to resolve objects

Recommended action: Verify if unresolved object is present in the database. If it isn't, check the object name or
add the object. If the object is present, transform the code manually.
+284 more
Issue 673: Unable to convert statements

Recommended action: Perform a manual conversion.
Databases.Eadpi.Schemas.dbo.Procedures.DELETE_MasterData_FA_SpecialCases
Databases.Eadpi.Schemas.dbo.Procedures.GET_Max_LocalReferenceNumber
Databases.Eadpi.Schemas.dbo.Procedures.INSERT_DeliveryCollection
Databases.Eadpi.Schemas.dbo.Procedures.INSERT_DeliveryCollection_CF

01/27/2021 9:39AM
Source database:
Databases.Eadpi.Schemas.dbo.Procedures.INSERT_DeliveryConditions
+9 more
Issue 810: MySQL doesn't support the SET NOCOUNT

Recommended action: If need try another way to send message back to the client application.
Databases.Eadpi.Schemas.dbo.Procedures.GET_OD_EADPI_vs_SAP
+10 more
Issue 823: MySQL doesn't support table hints in DML statements

Recommended action: Use MySQL methods of performance tuning.
+10 more
Issue 837: MySQL and MS SQL Server handle errors differently, so check result of code
conversion
Databases.Eadpi.Schemas.dbo.Procedures.GET_OD_EADPI_vs_SAP
+35 more
Issue 808: Unparsed SQL

Issue code: 808 | Number of occurrences: 2 | Estimated complexity: Complex
Databases.Eadpi.Schemas.dbo.Procedures.GET_OD_XML
Databases.Eadpi.Schemas.dbo.Procedures.GET_OD_XML_TO_WEB

01/27/2021 9:39AM
Source database:
Issue 811: Unable to convert functions

Recommended action: Create a user-defined function.
+10 more
Issue 9996: Internal Converter error occurred

Recommended action: Please submit report to developers.
Databases.Eadpi.Schemas.dbo.Procedures.INSERT_DeliveryConditions
Databases.Eadpi.Schemas.dbo.Procedures.INSERT_MasterData_FA_SpecialCases
Databases.Eadpi.Schemas.dbo.Procedures.UPDATE_DeliveryItems
Databases.Eadpi.Schemas.dbo.Procedures.UPDATE_DeliveryItems_CF
Databases.Eadpi.Schemas.dbo.Procedures.UPDATE_Delivery_Header_LocalReferenceNumber
Table-valued function Changes

Not all table-valued functions can be converted automatically. You'll need to address these issues manually.
Issue 646: MySQL doesn't support the COLLATE option. Automatic conversion ignores this
clause
Recommended action: You must use the COLLATION settings that were assigned when the database was
created.
Databases.Eadpi.Schemas.dbo.SQL table-valued functions.fnOutboundDeliveryItems
+5 more
Issue 659: The scope table-variables and temporary tables is different. You must apply
manual conversion, if you are using recursion
Documentation references: https://dev.mysql.com/doc/refman/5.7/en/data-types.html

01/27/2021 9:39AM
Source database:
Issue 663: Unable to resolve objects

Recommended action: Verify if unresolved object is present in the database. If it isn't, check the object name or
add the object. If the object is present, transform the code manually.
+19 more
Issue 647: Unable to convert analytic functions

Issue code: 647 | Number of occurrences: 1 | Estimated complexity: Medium

01/27/2021 9:39AM

Amazon Aurora (MySQL Compatible)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Amazon Aurora (MySQL Compatible)

Uploaded by

Copyright:

Available Formats

Database migration assessment report

Database objects with conversion actions for Amazon Aurora

Figure: Conversion statistics for database storage objects

Objects automatically converted Objects with simple actions

AWS Schema Conversion Tool Version 1.0.644 Page 1 of 6

Figure: Conversion statistics for database code objects

Objects automatically converted Objects with simple actions

Detailed recommendations for Amazon Aurora (MySQL compatible)

Storage object actions

Recommended action: Use non-clustered indexes.

Code object actions

Issue 663: Unable to resolve objects

Issue 673: Unable to convert statements

AWS Schema Conversion Tool Version 1.0.644 Page 3 of 6

Issue 810: MySQL doesn't support the SET NOCOUNT

Issue 823: MySQL doesn't support table hints in DML statements

Issue 808: Unparsed SQL

AWS Schema Conversion Tool Version 1.0.644 Page 4 of 6

Issue 811: Unable to convert functions

Issue 9996: Internal Converter error occurred

Table-valued function Changes

AWS Schema Conversion Tool Version 1.0.644 Page 5 of 6

Issue 663: Unable to resolve objects

Issue 647: Unable to convert analytic functions

AWS Schema Conversion Tool Version 1.0.644 Page 6 of 6

You might also like