Shulou(Shulou.com)06/03 Report--

How do I use DMS to migrate the RDS of AWS to Azure SQL? I believe that most people have not yet learned this skill, in order to let you learn, to give you a summary of the following content, do not say much, let's move on.

First of all, we have already created DMS, and then we just need to create any migration in DMS. Of course, before that, we need to make sure that the RDS of AWS is accessible, and create some test data in RDS, because RDS has no way to access local data files, so the script that generated the test data before can not be used. We can only build some test data manually.

After the test data is built, you can create a migration project directly in DMS, and migration project will define the source and destination of the migration.

You can see that AWS RDS for SQL Server can be selected in the options, and the corresponding target can be selected as Azure SQL. Here you can choose online migration, that is, continuous migration, which can support increments, and some migration scenarios do not support increments.

Enter information about the source database and the target database

It should be noted that whether it is RDS or Azure SQL, if you want to make DMS accessible, you need to add corresponding firewall rules. In fact, the IP of DMS will be prompted to remind you what the IP of DMS is when access is restricted.

Azure SQL can be added in firewall, and AWS RDS can be added in sg

You can see that the source library and the corresponding target library can be selected during migration

DMS's requirements for migration are relatively strict, the tables in the source database must exist in the target database, and the fields all require the same, there must be a primary key, the target table must be empty, and so on, which makes people feel very troublesome, but in fact, there are simple ways, which will be introduced later, and the most important point is that CDC must be opened.

CDC needs to be enabled at the library level first, just run the following command

Exec msdb.dbo.rds_cdc_enable_db Sample

After that, don't turn it on at the watch level.

USE Sample

EXEC sys.sp_cdc_enable_table

@ source_schema = Nintendbo`

@ source_name = Nobstestroomtable`

@ role_name = NULL

@ supports_net_changes = 1

Then there is no reminder that CDC is not open.

Confirm the previously entered information

You can see that the migration is already being prepared.

We try to add data to the source database

You can see in DMS that data is synchronized, which is a continuous process, as long as there is new data, but please note that if there is a new table, it will not be synchronized automatically, because it is up to the user to choose which tables to synchronize during DMS migration.

If you confirm that synchronization is no longer needed, you can choose cutover

After the migration is complete, you can also see the corresponding report

You can see that the use is relatively simple, mainly in the migration for the target library has a lot of restrictions, including primary keys, tables must exist and so on.

So far, we have successfully migrated AWS's RDS to Azure SQL using DMS. If you want to learn more skills or want to know more about it, please follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.