Amazon Technologies, Inc.

Igor Bekelman

Mykyta Sokolov

Vladyslav Tkachuk

Yuriy Yaroshenko

Irena Balin

Mykhailo Silin

Svitlana Malik

Krit Gupta

Harpreet Kaur Chawla

Justin Qoun Tang

Oleksandr Perepelytsya

Roman Yelysieiev

Prashant Agarwal

Vladislavs Tomasevs

Mehdi Naseri

Qi Cui

Denys Seliukov

Daniel Joseph Sheridan

Sathish Sampath

Michael Surkan

John Winford

Avijit Borthakur

Sunil Venkayala

A client of a database service may request a migration of a remote source database to a target database provided by the database service, where the source database and target database are published by a database vendor. Responsive to the request, a migration tool published by the database vendor may be selected from among multiple migration tools. The migration tool may derive a schema from the source database and create the target database according to the derive schema. The migration tool may then extract data of the source database using native application programming interfaces (APIs) provided by the vendor. The extracted data may then be imported into the target database using one or more additional native APIs. The migration tool may then initiate replication of transactions performed at the source database to the target database.

Managed service for database migration

Systems and techniques are disclosed for determining and provisioning and data resources for use in migrations data processing systems. Source data processing system metadata may be used to estimate data storage requirements for a migration and subtask parameters may be used to determine processing requirements. Migration resources may be determined based on these requirements and provisioned to perform migration operations. A migration may be monitored for resource utilization and resources allocated to the migration may be adjusted to increase migration efficiency and performance.

Replication system for data migration

Conversion to a virtual target may be performed for a source of a data store migration. A request that selects one of multiple data store conversion targets as a virtual target of data store migration from a source of the data store migration may be received. One or more conversion scripts for the data store migration may be generated based on an analysis of a possible conversion between the source of the data store migration and the virtual target of the data store migration using metadata obtained from the source of the data store migration that describes the source of the data store migration and a model corresponding to the virtual target of the data store migration. The conversion scripts may be stored for later execution.

Data store conversion from a source data store to a virtual target

Conversion that includes multiple targets or sources of a data store migration may be performed. A request that specifies a mapping between multiple sources and one or more targets, one or more sources and multiple targets, or multiple sources and multiple targets may be created for data store migration. Metadata may be obtained for the selected sources and targets for the mapping. Conversion scripts may then be generated for the mapping based on an analysis using the metadata. The conversion scripts may then be stored for later execution.

Multi-way data store conversion

Growing community of inventors

Redmond, WA, United States of America

Igor Bekelman