Migration guide: SAP ASE to Azure SQL Database

  • Article

Applies to: Azure SQL Database

In this guide, you learn how to migrate your SAP Adapter Server Enterprise (ASE) databases to an Azure SQL database by using SQL Server Migration Assistant for SAP Adapter Server Enterprise.

For other migration guides, see Azure Database Migration Guide.

Prerequisites

Before you begin migrating your SAP SE database to your SQL database, do the following:

Pre-migration

After you've met the prerequisites, you're ready to discover the topology of your environment and assess the feasibility of your migration.

Assess

By using SQL Server Migration Assistant (SSMA) for SAP Adaptive Server Enterprise (formally SAP Sybase ASE), you can review database objects and data, assess databases for migration, migrate Sybase database objects to your SQL database, and then migrate data to the SQL database. To learn more, see SQL Server Migration Assistant for Sybase (SybaseToSQL).

To create an assessment, do the following:

  1. Open SSMA for Sybase.

  2. Select File, and then select New Project.

  3. In the New Project pane, enter a name and location for your project and then, in the Migrate To drop-down list, select Azure SQL Database.

  4. Select OK.

  5. On the Connect to Sybase pane, enter the SAP connection details.

  6. Right-click the SAP database you want to migrate, and then select Create report. This generates an HTML report. Alternatively, you can select the Create report tab at the upper right.

  7. Review the HTML report to understand the conversion statistics and any errors or warnings. You can also open the report in Excel to get an inventory of SAP ASE objects and the effort that's required to perform schema conversions. The default location for the report is in the report folder within SSMAProjects. For example:

    drive:\<username>\Documents\SSMAProjects\MySAPMigration\report\report_<date>

Validate the type mappings

Before you perform schema conversion, validate the default data-type mappings or change them based on requirements. You can do so by selecting Tools > Project Settings, or you can change the type mapping for each table by selecting the table in the SAP ASE Metadata Explorer.

Convert the schema

To convert the schema, do the following:

  1. (Optional) To convert dynamic or specialized queries, right-click the node, and then select Add statement.

  2. Select the Connect to Azure SQL Database tab, and then enter the details for your SQL database. You can choose to connect to an existing database or provide a new name, in which case a database will be created on the target server.

  3. On the Sybase Metadata Explorer pane, right-click the SAP ASE schema you're working with, and then select Convert Schema.

  4. After the schema has been converted, compare and review the converted structure to the original structure identify potential problems.

    After the schema conversion, you can save this project locally for an offline schema remediation exercise. To do so, select File > Save Project. This gives you an opportunity to evaluate the source and target schemas offline and perform remediation before you publish the schema to your SQL database.

  5. On the Output pane, select Review results, and review any errors in the Error list pane.

  6. Save the project locally for an offline schema remediation exercise. To do so, select File > Save Project. This gives you an opportunity to evaluate the source and target schemas offline and perform remediation before you publish the schema to your SQL database.

Migrate the databases

After you have the necessary prerequisites in place and have completed the tasks associated with the pre-migration stage, you're ready to run the schema and data migration.

To publish the schema and migrate the data, do the following:

  1. Publish the schema. On the Azure SQL Database Metadata Explorer pane, right-click the database, and then select Synchronize with Database. This action publishes the SAP ASE schema to your SQL database.

  2. Migrate the data. On the SAP ASE Metadata Explorer pane, right-click the SAP ASE database or object you want to migrate, and then select Migrate Data. Alternatively, you can select the Migrate Data tab at the upper right.

    To migrate data for an entire database, select the check box next to the database name. To migrate data from individual tables, expand the database, expand Tables, and then select the check box next to the table. To omit data from individual tables, clear the check box.

  3. After the migration is completed, view the Data Migration Report.

  4. Validate the migration by reviewing the data and schema. To do so, connect to your SQL database by using SQL Server Management Studio.

Post-migration

After you've successfully completed the migration stage, you need to complete a series of post-migration tasks to ensure that everything is functioning as smoothly and efficiently as possible.

Remediate applications

After the data is migrated to the target environment, all the applications that formerly consumed the source need to start consuming the target. Accomplishing this will in some cases require changes to the applications.

Perform tests

The test approach to database migration consists of the following activities:

  1. Develop validation tests: To test the database migration, you need to use SQL queries. You must create the validation queries to run against both the source and target databases. Your validation queries should cover the scope you've defined.

  2. Set up a test environment: The test environment should contain a copy of the source database and the target database. Be sure to isolate the test environment.

  3. Run validation tests: Run validation tests against the source and the target, and then analyze the results.

  4. Run performance tests: Run performance tests against the source and the target, and then analyze and compare the results.

Optimize

The post-migration phase is crucial for reconciling any data accuracy issues, verifying completeness, and addressing performance issues with the workload.

For more information about these issues and the steps to mitigate them, see the Post-migration validation and optimization guide.

Next steps