Migrate from SAP ASE to Amazon RDS for SQL Server using AWS DMS - AWS Prescriptive Guidance
SummaryPrerequisites and limitationsArchitectureToolsEpicsRelated resources

Migrate from SAP ASE to Amazon RDS for SQL Server using AWS DMS

Created by Amit Kumar (AWS)

Environment: PoC or pilot

Source: SAP ASE

Target: Amazon RDS for SQL Server

R Type: Re-architect

Workload: SAP

Technologies: Migration; Databases; Modernization

AWS services: Amazon RDS; AWS DMS

Summary

This pattern provides guidance for migrating an SAP Adaptive Server Enterprise (ASE) database to an Amazon Relational Database Service (Amazon RDS) DB instance that's running Microsoft SQL Server. The source database can be located in an on-premises data center or on an Amazon Elastic Compute Cloud (Amazon EC2) instance. The pattern uses AWS Database Migration Service (AWS DMS) to migrate data and (optionally) computer-aided software engineering (CASE) tools to convert the database schema.

Prerequisites and limitations

Prerequisites

  • An active AWS account

  • An SAP ASE database in an on-premises data center or on an EC2 instance

  • A target Amazon RDS for SQL Server database that’s up and running

Limitations

  • Database size limit: 64 TB

Product versions

Architecture

Source technology stack

  • An SAP ASE database that's on premises or on an Amazon EC2 instance

Target technology stack

  • An Amazon RDS for SQL Server DB instance

Source and target architecture

From an SAP ASE database on Amazon EC2 to an Amazon RDS for SQL Server DB instance:

Target architecture for SAP ASE on Amazon EC2 to Amazon RDS for SQL Server

From an on-premises SAP ASE database to an Amazon RDS for SQL Server DB instance:

Target architecture for on-premises SAP ASE to Amazon RDS for SQL Server

Tools

  • AWS Database Migration Service (AWS DMS) is a web service you can use to migrate data from your database that is on-premises, on an Amazon RDS DB instance, or in a database on an EC2 instance, to a database on an AWS service such as Amazon RDS for SQL Server or an EC2 instance. You can also migrate a database from an AWS service to an on-premises database. You can migrate data between heterogeneous or homogeneous database engines.

  • For schema conversions, you can optionally use erwin Data Modeler or SAP PowerDesigner.

Epics

TaskDescriptionSkills required

Validate the source and target database versions.

DBA

Identify the storage requirements (storage type and capacity).

DBA, SysAdmin

Choose the proper instance type based on capacity, storage features, and network features.

DBA, SysAdmin

Identify the network access security requirements for the source and target databases.

DBA, SysAdmin

Identify the application migration strategy.

DBA, SysAdmin, App owner
TaskDescriptionSkills required

Create a virtual private cloud (VPC) and subnets.

SysAdmin

Create security groups and network access control lists (ACLs).

SysAdmin

Configure and start an Amazon RDS DB instance.

SysAdmin
TaskDescriptionSkills required

Migrate the database schema manually or use a CASE tool such as erwin Data Modeler or SAP PowerDesigner.

DBA
TaskDescriptionSkills required

Migrate data using AWS DMS.

DBA
TaskDescriptionSkills required

Follow the application migration strategy.

DBA, SysAdmin, App owner
TaskDescriptionSkills required

Switch the application clients over to the new infrastructure.

DBA, SysAdmin, App owner
TaskDescriptionSkills required

Shut down the temporary AWS resources.

DBA, SysAdmin

Review and validate the project documents.

DBA, SysAdmin, App owner

Gather metrics such as time to migrate, percentage of manual versus automated tasks, and cost savings.

DBA, SysAdmin, App owner

Close out the project and provide feedback.

DBA, SysAdmin, App owner

Related resources

References

Tutorials and videos