Cloud concept · Updated

Homogeneous Migration - Homogeneous migration moves a database between environments while retaining the same database engine, such as PostgreSQL to PostgreSQL.

In short

A homogeneous migration changes where a database runs without changing its underlying engine family. It generally reduces schema conversion and application rewrite work compared with moving between different engines, but still requires compatibility checks, data validation, and a controlled cutover.

Cloud Concepts Hub →

5 key aspects of Homogeneous Migration

Homogeneous migration preserves the database engine while requiring deliberate compatibility checks, transfer planning, validation, and cutover control.

01
Database engine continuity

The source and target retain the same database engine family. A version or hosting change does not automatically make the migration heterogeneous, although version compatibility still needs verification.

02
Reduced conversion effort

Existing schemas and application queries generally require fewer changes than they would in a cross-engine migration. Check extensions, stored code, and service restrictions rather than assuming everything will work unchanged.

03
Flexible data-transfer methods

Native exports, supported backups, or migration tools can transfer the data. Choose a method based on database size, engine support, available bandwidth, and the acceptable maintenance window.

04
Downtime and replication planning

An initial load followed by change data capture can reduce downtime when supported. Replication lag, source log retention, and final write coordination determine whether the cutover can meet the outage target.

05
Validation and controlled cutover

Validate data completeness, application behavior, permissions, and performance before switching production traffic. Define rollback criteria and account for new target-side writes after cutover.

Cloud services for Homogeneous Migration

Amazon RDS or a database installed on Amazon EC2 can serve as the target for a same-engine migration. AWS DMS can move data between supported endpoints and, where supported, replicate ongoing changes to reduce the cutover window. Native database utilities may be preferable for some backup, restore, or schema-transfer tasks. These services do not eliminate compatibility checks: engineers must configure connectivity and permissions, validate database objects and data, test application behavior, and coordinate the final connection switch.

Amazon RDSAmazon RDS

Amazon RDS can host the target database while retaining the source engine, such as PostgreSQL to RDS for PostgreSQL or MySQL to RDS for MySQL. Validate supported versions, extensions, privileges, and import methods before selecting the target configuration.

Amazon EC2Amazon EC2

Amazon EC2 can host a self-managed source or target database using the same engine. It provides more operating-system and database-level control than a managed database service, but engineers remain responsible for database maintenance, backups, and availability design.

Homogeneous Migration exam questions

Real practice exam questions on Homogeneous Migration, with the correct answer and its explanation. Answer them with every option in the exam simulator.

CLF-C02

A company plans to move a small, on-premises MySQL database to Amazon RDS for MySQL. The database includes stored procedures that the application must continue using. A maintenance window allows enough time to stop application writes and export and import the entire database. Which migration plan avoids unnecessary conversion work while preserving the application's database behavior?

Show answerCORRECT ANSWER

Check target version and feature compatibility, use MySQL-native tools to export and import the schema and data, and validate the database before switching the application.

Keeping MySQL as the source and target engine permits a homogeneous migration using native tools. The export should include required objects such as stored procedures. Compatibility checks and validation are still necessary, and the maintenance window makes a stopped-write export and import practical.

SAA-C03

A company runs an on-premises PostgreSQL database for a continuously used billing application. The application depends on PostgreSQL-specific functions, views, and triggers. The company wants to reduce database administration costs by moving to a managed AWS database. Its migration budget does not allow for rewriting database code. An assessment confirms that all required database objects and features are supported by the corresponding Amazon RDS engine version.

The target database is empty. The initial data transfer will take several hours, during which the application must continue accepting writes. The company allows a brief interruption for final synchronization and endpoint changes.

Which migration plan meets these requirements?

Show answerCORRECT ANSWER

Create an RDS for PostgreSQL DB instance. Use native PostgreSQL tools to deploy the required schema and database code. Configure AWS DMS for full load and ongoing change replication, ensuring that target triggers do not duplicate replicated changes. Pause source writes, let replication catch up, validate, and redirect the application.

Keeping PostgreSQL avoids an engine conversion and the associated application rewrite effort. Native schema tools can deploy functions, views, and triggers that a standard DMS data migration does not fully migrate. Full load with change data capture transfers the initial data while preserving subsequent writes. Controlling target trigger execution prevents replicated changes from producing duplicate effects, and a controlled cutover limits downtime.

SAP-C03

A software company is migrating two independent applications to AWS. One application will move from self-managed PostgreSQL to Amazon RDS for PostgreSQL without changing database engines. The other application will move from Microsoft SQL Server to Amazon Aurora PostgreSQL-Compatible Edition. Both databases contain tables, views, stored procedures, and functions that the applications require.

A compatibility assessment confirms that the first application's objects are supported on its target. For the second application, most database code objects can be converted automatically, but some require manual changes. The company has configured AWS Database Migration Service (AWS DMS) for full load and ongoing replication for both databases. The migration team must prepare and test the target schemas before starting data replication.

Which approach meets these requirements with the LEAST manual schema-rewriting effort?

Show answerCORRECT ANSWER

Use a native PostgreSQL schema-only export and restore for the first application. Use DMS Schema Conversion for the second application's schema and supported database code objects, resolve conversion issues, and apply the converted objects. Test both target schemas and configure the DMS tasks to preserve the pre-created tables.

Native database tools can move schemas between databases that use the same engine. DMS Schema Conversion handles heterogeneous schema conversion, including supported views, stored procedures, functions, and data types, reducing manual rewriting. Conversion issues still require review and remediation. Preserving the pre-created target tables keeps the prepared schemas in place during data migration.

Practice Homogeneous Migration in a full exam

Questions on Homogeneous Migration in each practice exam, with every answer option and an explanation for each:

Start a free practice exam

What is Homogeneous Migration

2 min read

Homogeneous migration is a database migration in which the source and target use the same database engine, such as MySQL to MySQL, PostgreSQL to PostgreSQL, or Oracle Database to Oracle Database. The infrastructure, operating environment, or database version can change without changing this classification. By contrast, moving Oracle Database to PostgreSQL is a heterogeneous migration because the database engine changes.

In the cloud, this approach commonly moves an on-premises database to a managed database service or to a database running on a virtual machine. For example, a company might migrate a self-managed PostgreSQL database to Amazon RDS for PostgreSQL. The application retains its PostgreSQL database interface, while responsibility for tasks such as infrastructure maintenance and automated backups shifts toward the managed service. Homogeneous migrations can also occur between cloud environments or between accounts and Regions.

The main benefit is reduced conversion effort. Tables, SQL statements, and application data-access logic are more likely to remain usable when the engine stays the same. However, same-engine does not mean identical behavior or complete compatibility. Engineers must check supported versions, extensions, character sets, collations, authentication methods, and database configuration. Managed services can restrict administrative privileges, filesystem access, or extensions that were available on the original server.

The transfer method depends on database size, acceptable downtime, and engine capabilities. A small database with a generous maintenance window might use a native logical export and import. Larger databases might use supported backup-and-restore procedures or an initial data load followed by change data capture. Change data capture copies ongoing source changes while applications continue using the original database, reducing the final interruption. It requires supported configurations and enough source log retention to avoid losing changes before they are applied.

For example, an online retailer migrating MySQL to Amazon RDS for MySQL could use AWS Database Migration Service to load existing data and replicate subsequent changes. Before cutover, engineers would test the application, compare source and target data, and monitor replication lag. They would then stop or carefully coordinate writes, wait for remaining changes to apply, switch application connections, and verify transactions against the target. A rollback plan must account for any writes accepted by the target after the switch.

A common misconception is that homogeneous migration guarantees zero downtime or automatically transfers every database object. Actual behavior depends on the migration tool and engine combination. Users, permissions, indexes, triggers, stored procedures, and scheduled jobs may require separate handling. Retaining the engine also does not guarantee the same performance: storage latency, instance sizing, network placement, and configuration can change query behavior.

For certification questions, identify the source and target engines first. Same-engine moves are homogeneous; different-engine moves are heterogeneous. AWS Database Migration Service supports both categories for supported endpoints. Schema conversion is generally associated with heterogeneous migration, rather than being the defining requirement for a homogeneous move. Choose the migration approach based on compatibility, downtime requirements, operational effort, and validation needs, not merely the shared engine name.

Learn Homogeneous Migration in lessons

6 short lessons on Homogeneous Migration in 3 certification courses.

Open the lessons