Phase 1: Prepare
Assess the source SAP ASE database architecture to understand its dependencies and current state.
Assess the source database
To assess the source database, such as objects, users, and permissions, you can use third-party tools. For more information, see Preparation and assessment for migrating from SAP ASE to Amazon Aurora MySQL.
-
Analyze the code conversion by listing all of the application dependencies and interfaces.
-
Identify SAP application dependencies that are only supported in SAP. You may need to find an alternative method to work with Microsoft SQL.
-
Identify communication protocols.
-
Identify replication requirements and high availability/disaster recovery compliance.
-
Identify security compliance and encryption protocols.
You can use any third-party migration tool for converting the schema code, such as
SAP ASE database or Amazon RDS for SQL Server. You must convert some code manually, such as
non-ANSI SQL, because SQL Server may not support it. After you convert the code,
conduct unit and functional testing to validate database objects. For more
information, see Migrate your SAP ASE (Sybase ASE) database to Amazon RDS for SQL Server
Evaluate security concerns
SQL Server offers various security options that are based on enterprise compliance requirements and unique use cases. For more information, see the following documents about the security of SQL Server:
Consult AWS Partners
To reduce migration times, consider consulting with AWS Database Migration Service Partners
Based on your requirements and preferences, partners can provide tools and advice for how to handle migrations or troubleshoot migration aspects. Ensure that you follow AWS best practices to host your database in the AWS Cloud. For more information, see Best practices for Amazon RDS.
