0

I'm using a SQL Server on-prem source for a DMS to replicate to a SQL Server RDS. Every night, at about midnight, I'm seeing a spike of ~1.6M CDC incoming changes on my DMS task, but nothing is making anywhere near that many data changes on-prem. It takes about 8hr to get caught up, with a max latency of about 5hr. The latency hits its max about an hour or two before it's caught back up. Otherwise, it seems caught up for the remainder of the day. Also comparing the count of the PK column of one of the main tables, I'm about 65.6k records short in my RDS.

I don't have CDC on at the source db level or any of the source tables, but I thought I didn't need it because all tables being replicated have PKs

Improve this question
3
  • You've described a number of happenings but does your question have a question? Commented Jun 25, 2024 at 21:47
  • There is some churn. Can you trace your source for a day? Commented Jul 1, 2024 at 23:46
  • Ran a trace on the source. Implementing some changes to some nightly processes to see if they are the source of the data changes Commented Jul 8, 2024 at 18:07
Related questions
2
AWS DMS continuous replication latency question
1
AWS DMS - Migrate existing data and replicate on-going changes
0
Get data and control records using AWS DMS with Kafka as the target
Load 4 more related questions Show fewer related questions

0

Reset to default

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.