New – A Fully Managed Schema Conversion in Amazon Web Services Database Migration Service

{"value":"Since we [launched ](https://aws.amazon.com/blogs/aws/aws-database-migration-service/)Amazon Web Services Database Migration Service (Amazon Web Services DMS) in 2016, customers have securely migrated more than 800,000 databases to Amazon Web Services with minimal downtime. [Amazon Web Services DMS](https://aws.amazon.com/dms/) supports migration between 20+ database and analytics engines, such as [Oracle to Amazon Aurora MySQL](https://docs.aws.amazon.com/dms/latest/sbs/chap-on-premoracle2aurora.html), [MySQL to Amazon Relational Database (Amazon RDS) MySQL](https://docs.aws.amazon.com/dms/latest/sbs/chap-manageddatabases.mysql2rds.html), [Microsoft SQL Server to Amazon Aurora PostgreSQL](https://d1.awsstatic.com/whitepapers/Migration/sql-server-database-amazon-aurora-postgresql-migration-playbook-12.4.pdf?refid=cr_card), [MongoDB to Amazon DocumentDB](https://docs.aws.amazon.com/dms/latest/sbs/chap-mongodb2documentdb.html), [Oracle to Amazon Redshift](https://aws.amazon.com/getting-started/hands-on/migrate-oracle-to-amazon-redshift/), and [to and from Amazon Simple Storage Service (Amazon S3).](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Target.S3.html)\n\nSpecifically, the [Amazon Web Services Schema Conversion Tool ](https://aws.amazon.com/dms/schema-conversion-tool/)(Amazon Web Services SCT) makes heterogeneous database and data warehouse migrations predictable and can automatically convert the source schema and a majority of the database code objects, including views, stored procedures, and functions, to a format compatible with the target engine. For example, it supports the conversion of Oracle PL/SQL and SQL Server T-SQL code to equivalent code in the [Amazon Aurora](https://aws.amazon.com/cn/rds/aurora/?trk=cndc-detail) MySQL dialect of SQL or the equivalent PL/pgSQL code in PostgreSQL. You can download the Amazon Web Services SCT for your platform, including Windows or Linux (Fedora and Ubuntu).\n\nToday we announce fully managed [Amazon Web Services DMS Schema Conversion](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_SchemaConversion.html), which streamlines database migrations by making schema assessment and conversion available inside Amazon Web Services DMS. With DMS Schema Conversion, you can now plan, assess, convert and migrate under one central DMS service. You can access features of DMS Schema Conversion in the Amazon Web Services Management Console without downloading and executing Amazon Web Services SCT.\n\nAmazon Web Services DMS Schema Conversion automatically converts your source database schemas, and a majority of the database code objects to a format compatible with the target database. This includes tables, views, stored procedures, functions, data types, synonyms, and so on, similar to Amazon Web Services SCT. Any objects that cannot be automatically converted are clearly marked as action items with prescriptive instructions on how to migrate to Amazon Web Services manually.\n\nIn this launch, DMS Schema Conversion supports the following databases as sources for migration projects:\n\n- Microsoft SQL Server version 2008 R2 and higher\n- Oracle version 10.2 and later, 11g and up to 12.2, 18c, and 19c\n- DMS Schema Conversion supports the following databases as targets for migration projects:\n- \n- [Amazon RDS](https://aws.amazon.com/cn/rds/?trk=cndc-detail) for MySQL version 8.x\n- [Amazon RDS](https://aws.amazon.com/cn/rds/?trk=cndc-detail) for PostgreSQL version 14.x\n\n**++Setting Up Amazon Web Services DMS Schema Conversion++**\n\nTo get started with DMS Schema Conversion, and if it is your first time using Amazon Web Services DMS, complete the setup tasks to create a virtual private cloud (VPC) using the [Amazon VPC](https://aws.amazon.com/vpc) service, source, and target database. To learn more, see [Prerequisites for Amazon Web Services Database Migration Service](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_GettingStarted.Prerequisites.html) in the Amazon Web Services documentation.\n\nIn the Amazon Web Services DMS console, you can see new menus to set up **Instance profiles**, add **Data providers**, and create **Migration projects**.\n\nBefore you create your migration project, set up an instance profile by choosing** Instance profiles** in the left pane. An instance profile specifies network and security settings for your DMS Schema Conversion instances. You can create multiple instance profiles and select an instance profile to use for each migration project.\n\n\n\nChoose **Create instance profile** and specify your default VPC or a new VPC, [Amazon Simple Storage Service](https://aws.amazon.com/s3) ([Amazon S3](https://aws.amazon.com/cn/s3/?trk=cndc-detail)) bucket to store your schema conversion metadata, and additional settings such as [Amazon Web Services Key Management Service ](https://aws.amazon.com/kms)(Amazon Web Services KMS) keys.\n\nYou can create the simplest network configuration with a single VPC configuration. If your source or target data providers are in different VPCs, you can create your instance profile in one of the VPCs, and then link these two VPCs by using VPC peering.\n\n\n\nNext, you can add data providers that store the data store type and location information about your source and target databases by choosing **Data providers **in the left pane. For each database, you can create a single data provider and use it in multiple migration projects.\n\nYour data provider can be a fully managed [Amazon RDS](https://aws.amazon.com/cn/rds/?trk=cndc-detail) instance or a self-managed engine running either on-premises or on an [Amazon Elastic Compute Cloud](https://aws.amazon.com/ec2) (Amazon EC2) instance.\n\n\n\nChoose **Create data provider** to create a new data provider. You can set the type of the database location manually, such as database engine, domain name or IP address, port number, database name, and so on, for your data provider. Here, I have selected an **RDS database instance**.\n\n\n\nAfter you create a data provider, make sure that you add database connection credentials in [Amazon Web Services Secrets Manager](https://aws.amazon.com/secrets-manager/). DMS Schema Conversion uses this information to connect to a database.\n\n**++Converting your database schema with Amazon Web Services DMS Schema Conversion++**\n\nNow, you can create a migration project for DMS Schema Conversion by choosing **Migration projects** in the left pane. A migration project describes your source and target data providers, your instance profile, and migration rules. You can also create multiple migration projects for different source and target data providers.\n\n\n\nChoose **Create migration project** and select your instance profile and source and target data providers for DMS Schema Conversion.\n\n\n\nAfter creating your migration project, you can use the project to create assessment reports and convert your database schema. Choose your migration project from the list, then choose the **Schema conversion** tab and click **Launch schema conversion**.\n\n\n\nMigration projects in DMS Schema Conversion are always serverless. This means that Amazon Web Services DMS automatically provisions the cloud resources for your migration projects, so you don’t need to manage schema conversion instances.\n\nOf course, the first launch of DMS Schema Conversion requires starting a schema conversion instance, which can take up to 10–15 minutes. This process also reads the metadata from the source and target databases. After a successful first launch, you can access DMS Schema Conversion faster.\n\n\n\nAn important part of DMS Schema Conversion is that it generates a database migration assessment report that summarizes all of the schema conversion tasks. It also details the action items for schema that cannot be converted to the DB engine of your target database instance. You can view the report in the Amazon Web Services DMS console or export it as a comma-separated value (.csv) file.\n\nTo create your assessment report, choose the source database schema or schema items that you want to assess. After you select the checkboxes, choose **Assess **in the **Actions **menu in the source database pane. This report will be archived with .csv files in your S3 bucket. To change the S3 bucket, edit the schema conversion settings in your instance profile.\n\nThen, you can apply the converted code to your target database or save it as a SQL script. To apply converted code, choose **Convert** in the pane of **Source data provider** and then **Apply changes** in the pane of **Target data provider**.\n\nOnce the schema has been converted successfully, you can move on to the database migration phase using Amazon Web Services DMS. To learn more, see [Getting started with Amazon Web Services Database Migration Service](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_GettingStarted.html#CHAP_GettingStarted.Dashboard) in the Amazon Web Services documentation.\n\n**++Now Available++**\n\nAmazon Web Services DMS Schema Conversion is now available in the US East (Ohio), US East (N. Virginia), US West (Oregon), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Europe (Frankfurt), Europe (Ireland), and Europe (Stockholm) Regions, and you can start using it today.\n\nTo learn more, see the [Amazon Web Services DMS Schema Conversion User Guide](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_SchemaConversion.html), give it a try, and please send feedback to[ Amazon Web Services re:Post for AWS DMS](https://repost.aws/tags/TAloTfMMIZRtqwjRAie3cDVg/aws-database-migration-service) or through your usual Amazon Web Services support contacts.\n\n– [Channy](http://twitter.com/channyun)\n\n\n\n### [Channy Yun](https://aws.amazon.com/blogs/aws/author/channy-yun/)\n\nChanny Yun is a Principal Developer Advocate for Amazon Web Services, and passionate about helping developers to build modern applications on latest Amazon Web Services services. A pragmatic developer and blogger at heart, he loves community-driven learning and sharing of technology, which has funneled developers to global Amazon Web Services Usergroups. His main topics are open-source, container, storage, network & security, and IoT. Follow him on Twitter at @channyun.","render":"<p>Since we <a href=\\"https://aws.amazon.com/blogs/aws/aws-database-migration-service/\\" target=\\"_blank\\">launched </a>Amazon Web Services Database Migration Service (Amazon Web Services DMS) in 2016, customers have securely migrated more than 800,000 databases to Amazon Web Services with minimal downtime. <a href=\\"https://aws.amazon.com/dms/\\" target=\\"_blank\\">Amazon Web Services DMS</a> supports migration between 20+ database and analytics engines, such as <a href=\\"https://docs.aws.amazon.com/dms/latest/sbs/chap-on-premoracle2aurora.html\\" target=\\"_blank\\">Oracle to Amazon Aurora MySQL</a>, <a href=\\"https://docs.aws.amazon.com/dms/latest/sbs/chap-manageddatabases.mysql2rds.html\\" target=\\"_blank\\">MySQL to Amazon Relational Database (Amazon RDS) MySQL</a>, <a href=\\"https://d1.awsstatic.com/whitepapers/Migration/sql-server-database-amazon-aurora-postgresql-migration-playbook-12.4.pdf?refid=cr_card\\" target=\\"_blank\\">Microsoft SQL Server to Amazon Aurora PostgreSQL</a>, <a href=\\"https://docs.aws.amazon.com/dms/latest/sbs/chap-mongodb2documentdb.html\\" target=\\"_blank\\">MongoDB to Amazon DocumentDB</a>, <a href=\\"https://aws.amazon.com/getting-started/hands-on/migrate-oracle-to-amazon-redshift/\\" target=\\"_blank\\">Oracle to Amazon Redshift</a>, and <a href=\\"https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Target.S3.html\\" target=\\"_blank\\">to and from Amazon Simple Storage Service (Amazon S3).</a></p>\\n<p>Specifically, the <a href=\\"https://aws.amazon.com/dms/schema-conversion-tool/\\" target=\\"_blank\\">Amazon Web Services Schema Conversion Tool </a>(Amazon Web Services SCT) makes heterogeneous database and data warehouse migrations predictable and can automatically convert the source schema and a majority of the database code objects, including views, stored procedures, and functions, to a format compatible with the target engine. For example, it supports the conversion of Oracle PL/SQL and SQL Server T-SQL code to equivalent code in the [Amazon Aurora](https://aws.amazon.com/cn/rds/aurora/?trk=cndc-detail) MySQL dialect of SQL or the equivalent PL/pgSQL code in PostgreSQL. You can download the Amazon Web Services SCT for your platform, including Windows or Linux (Fedora and Ubuntu).</p>\\n<p>Today we announce fully managed <a href=\\"https://docs.aws.amazon.com/dms/latest/userguide/CHAP_SchemaConversion.html\\" target=\\"_blank\\">Amazon Web Services DMS Schema Conversion</a>, which streamlines database migrations by making schema assessment and conversion available inside Amazon Web Services DMS. With DMS Schema Conversion, you can now plan, assess, convert and migrate under one central DMS service. You can access features of DMS Schema Conversion in the Amazon Web Services Management Console without downloading and executing Amazon Web Services SCT.</p>\\n<p>Amazon Web Services DMS Schema Conversion automatically converts your source database schemas, and a majority of the database code objects to a format compatible with the target database. This includes tables, views, stored procedures, functions, data types, synonyms, and so on, similar to Amazon Web Services SCT. Any objects that cannot be automatically converted are clearly marked as action items with prescriptive instructions on how to migrate to Amazon Web Services manually.</p>\n<p>In this launch, DMS Schema Conversion supports the following databases as sources for migration projects:</p>\n<ul>\\n<li>Microsoft SQL Server version 2008 R2 and higher</li>\n<li>Oracle version 10.2 and later, 11g and up to 12.2, 18c, and 19c</li>\n<li>DMS Schema Conversion supports the following databases as targets for migration projects:</li>\n<li></li>\n<li>Amazon RDS for MySQL version 8.x</li>\n<li>Amazon RDS for PostgreSQL version 14.x</li>\n</ul>\\n<p><strong><ins>Setting Up Amazon Web Services DMS Schema Conversion</ins></strong></p>\n<p>To get started with DMS Schema Conversion, and if it is your first time using Amazon Web Services DMS, complete the setup tasks to create a virtual private cloud (VPC) using the <a href=\\"https://aws.amazon.com/vpc\\" target=\\"_blank\\">Amazon VPC</a> service, source, and target database. To learn more, see <a href=\\"https://docs.aws.amazon.com/dms/latest/userguide/CHAP_GettingStarted.Prerequisites.html\\" target=\\"_blank\\">Prerequisites for Amazon Web Services Database Migration Service</a> in the Amazon Web Services documentation.</p>\\n<p>In the Amazon Web Services DMS console, you can see new menus to set up <strong>Instance profiles</strong>, add <strong>Data providers</strong>, and create <strong>Migration projects</strong>.</p>\\n<p>Before you create your migration project, set up an instance profile by choosing** Instance profiles** in the left pane. An instance profile specifies network and security settings for your DMS Schema Conversion instances. You can create multiple instance profiles and select an instance profile to use for each migration project.</p>\n<p><img src=\\"https://dev-media.amazoncloud.cn/8a7d6cc9a1214138a0c3a70780cbb70d_image.png\\" alt=\\"image.png\\" /></p>\n<p>Choose <strong>Create instance profile</strong> and specify your default VPC or a new VPC, <a href=\\"https://aws.amazon.com/s3\\" target=\\"_blank\\">Amazon Simple Storage Service</a> ([Amazon S3](https://aws.amazon.com/cn/s3/?trk=cndc-detail)) bucket to store your schema conversion metadata, and additional settings such as <a href=\\"https://aws.amazon.com/kms\\" target=\\"_blank\\">Amazon Web Services Key Management Service </a>(Amazon Web Services KMS) keys.</p>\\n<p>You can create the simplest network configuration with a single VPC configuration. If your source or target data providers are in different VPCs, you can create your instance profile in one of the VPCs, and then link these two VPCs by using VPC peering.</p>\n<p><img src=\\"https://dev-media.amazoncloud.cn/f47ab4c554e84ff49ad7946aff06bd1e_image.png\\" alt=\\"image.png\\" /></p>\n<p>Next, you can add data providers that store the data store type and location information about your source and target databases by choosing **Data providers **in the left pane. For each database, you can create a single data provider and use it in multiple migration projects.</p>\n<p>Your data provider can be a fully managed Amazon RDS instance or a self-managed engine running either on-premises or on an <a href=\\"https://aws.amazon.com/ec2\\" target=\\"_blank\\">Amazon Elastic Compute Cloud</a> (Amazon EC2) instance.</p>\\n<p><img src=\\"https://dev-media.amazoncloud.cn/7d816feef4c4426fb8e0de63d7e2a021_image.png\\" alt=\\"image.png\\" /></p>\n<p>Choose <strong>Create data provider</strong> to create a new data provider. You can set the type of the database location manually, such as database engine, domain name or IP address, port number, database name, and so on, for your data provider. Here, I have selected an <strong>RDS database instance</strong>.</p>\\n<p><img src=\\"https://dev-media.amazoncloud.cn/e09aee5a63924619813091c0244e2c45_image.png\\" alt=\\"image.png\\" /></p>\n<p>After you create a data provider, make sure that you add database connection credentials in <a href=\\"https://aws.amazon.com/secrets-manager/\\" target=\\"_blank\\">Amazon Web Services Secrets Manager</a>. DMS Schema Conversion uses this information to connect to a database.</p>\\n<p><strong><ins>Converting your database schema with Amazon Web Services DMS Schema Conversion</ins></strong></p>\n<p>Now, you can create a migration project for DMS Schema Conversion by choosing <strong>Migration projects</strong> in the left pane. A migration project describes your source and target data providers, your instance profile, and migration rules. You can also create multiple migration projects for different source and target data providers.</p>\\n<p><img src=\\"https://dev-media.amazoncloud.cn/52ff4c59d1a4480aaf2c2cc542d394f5_image.png\\" alt=\\"image.png\\" /></p>\n<p>Choose <strong>Create migration project</strong> and select your instance profile and source and target data providers for DMS Schema Conversion.</p>\\n<p><img src=\\"https://dev-media.amazoncloud.cn/ecc888b30de5495db2bcc88ea56ade95_image.png\\" alt=\\"image.png\\" /></p>\n<p>After creating your migration project, you can use the project to create assessment reports and convert your database schema. Choose your migration project from the list, then choose the <strong>Schema conversion</strong> tab and click <strong>Launch schema conversion</strong>.</p>\\n<p><img src=\\"https://dev-media.amazoncloud.cn/676ec967cb6b4541a597f8a568641a22_image.png\\" alt=\\"image.png\\" /></p>\n<p>Migration projects in DMS Schema Conversion are always serverless. This means that Amazon Web Services DMS automatically provisions the cloud resources for your migration projects, so you don’t need to manage schema conversion instances.</p>\n<p>Of course, the first launch of DMS Schema Conversion requires starting a schema conversion instance, which can take up to 10–15 minutes. This process also reads the metadata from the source and target databases. After a successful first launch, you can access DMS Schema Conversion faster.</p>\n<p><img src=\\"https://dev-media.amazoncloud.cn/56e284d84246448abf62fff8af1be6de_image.png\\" alt=\\"image.png\\" /></p>\n<p>An important part of DMS Schema Conversion is that it generates a database migration assessment report that summarizes all of the schema conversion tasks. It also details the action items for schema that cannot be converted to the DB engine of your target database instance. You can view the report in the Amazon Web Services DMS console or export it as a comma-separated value (.csv) file.</p>\n<p>To create your assessment report, choose the source database schema or schema items that you want to assess. After you select the checkboxes, choose **Assess **in the **Actions **menu in the source database pane. This report will be archived with .csv files in your S3 bucket. To change the S3 bucket, edit the schema conversion settings in your instance profile.</p>\n<p>Then, you can apply the converted code to your target database or save it as a SQL script. To apply converted code, choose <strong>Convert</strong> in the pane of <strong>Source data provider</strong> and then <strong>Apply changes</strong> in the pane of <strong>Target data provider</strong>.</p>\\n<p>Once the schema has been converted successfully, you can move on to the database migration phase using Amazon Web Services DMS. To learn more, see <a href=\\"https://docs.aws.amazon.com/dms/latest/userguide/CHAP_GettingStarted.html#CHAP_GettingStarted.Dashboard\\" target=\\"_blank\\">Getting started with Amazon Web Services Database Migration Service</a> in the Amazon Web Services documentation.</p>\\n<p><strong><ins>Now Available</ins></strong></p>\n<p>Amazon Web Services DMS Schema Conversion is now available in the US East (Ohio), US East (N. Virginia), US West (Oregon), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Europe (Frankfurt), Europe (Ireland), and Europe (Stockholm) Regions, and you can start using it today.</p>\n<p>To learn more, see the <a href=\\"https://docs.aws.amazon.com/dms/latest/userguide/CHAP_SchemaConversion.html\\" target=\\"_blank\\">Amazon Web Services DMS Schema Conversion User Guide</a>, give it a try, and please send feedback to<a href=\\"https://repost.aws/tags/TAloTfMMIZRtqwjRAie3cDVg/aws-database-migration-service\\" target=\\"_blank\\"> Amazon Web Services re:Post for AWS DMS</a> or through your usual Amazon Web Services support contacts.</p>\\n<p>– <a href=\\"http://twitter.com/channyun\\" target=\\"_blank\\">Channy</a></p>\\n<p><img src=\\"https://dev-media.amazoncloud.cn/c8c2c88fa7814c659e0342e75c05ca3c_image.png\\" alt=\\"image.png\\" /></p>\n<h3><a id=\\"Channy_Yunhttpsawsamazoncomblogsawsauthorchannyyun_83\\"></a><a href=\\"https://aws.amazon.com/blogs/aws/author/channy-yun/\\" target=\\"_blank\\">Channy Yun</a></h3>\\n<p>Channy Yun is a Principal Developer Advocate for Amazon Web Services, and passionate about helping developers to build modern applications on latest Amazon Web Services services. A pragmatic developer and blogger at heart, he loves community-driven learning and sharing of technology, which has funneled developers to global Amazon Web Services Usergroups. His main topics are open-source, container, storage, network &amp; security, and IoT. Follow him on Twitter at @channyun.</p>\n"}