Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

Migrate with DMS EC2 SQL server to RDS SQL

0

I am trying to migrate a SQL Server database hosted on an EC2 instance to an RDS SQL using DMS, but in the logs I get a particular error "The database 'rdsadmin' does not exist" which I do not understand why it is looking for that database of data in the source of the EC2 instance if the one that should contain an rdsadmin database is the RDS destination. Seeing this error, I generated a database "rdsadmin" in the EC2 instance so that the process could advance but when it advanced it gave another error "The stored procedure 'rdsadmin.dbo.rds_show_configuration' was not found" and "The SELECT permission was denied in the object 'fn_dblog', database 'mssqlsystemresource', schema 'sys'"

Therefore, I am left wondering if there is a bug with the DMS version "3.5.1" because, as indicated, the source is an EC2 sql server instance and the destination is an RDS sql.

As additional information, the source database is a Windows Server 2012 and the destination RDS is Windows Server 2016 and if I do a restore manually it works without problem but I am interested in maintaining the synchronization of the data with the DMS.

I remain attentive if you have any information about a similar case so that I can move forward in activating the DMS.

  • joanarbelaez
    2 years ago

    I installed version N-1 of the DMS and only activated the data replication from source to destination in the task but it gives me the error "The metadata could not be determined because the 'EXECUTE pr_GeneraCorreosAlum @rut' instruction of the procedure 'tr_tr_tg_personas' causes a indirect recursion. Line: 1 Column: -1 [1022502] (ar_odbc_stmt.c:3932)" and the replication task fails

Topics
Migration & ModernizationComputeDatabase
Tags
Microsoft SQL ServerAWS Database Migration ServiceWindowsRDS Custom for SQL Server
Language
English
asked 2 years ago2.1K views
1 Answer
1
Accepted Answer

I solved the problem by deactivating the table trigger in the RDS destination so that it does not generate recursion, lowering the DMS version and the replica became operational

answered 2 years ago
EXPERT
reviewed 2 years ago
EXPERT
reviewed 2 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Relevant content