Change Data Capture Anomalies

Bobby P 231 Reputation points
2022-08-10T13:34:38.447+00:00

We have noticed some holes when capturing some of our database changes captured via Change Data Capture(CDC) functions and pumping that data to our "Silo" Database where we combine some of our data touch points from our "Database of Truth".

Has anyone seen or experienced any holes in CDC and maybe some anomalies that appear sometimes when trying to capture changed data through CDC functions?

Soooo it looks like in order to fix these anomalies...like a payment method that is either wrong or missing for example...it looks like we're going to have to sweep through the "Database of Truth" and our "Silo" Database in order to fix them.

Just wondering if anyone else has experienced CDC anomalies, gaps before and how they may have gone about fixing them.

Thanks in advance for your review and am hopeful for aa reply.

Developer technologies Transact-SQL
SQL Server Other
{count} votes

2 answers

Sort by: Most helpful
  1. Tom Phillips 17,771 Reputation points
    2022-08-10T16:21:32.433+00:00

    I have used CDC extensively and have never had the issue you describe unless someone has turned off CDC for a period of time.

    The only way to recover your data is to pull the current data from the source system.

    How are you getting and applying the changes to the target? This is much more likely a problem in your processing of the changes, than CDC not capturing the changes.

    0 comments No comments

  2. XYJ XYJ 1 Reputation point
    2022-08-11T06:00:48.577+00:00

    Hi,

    To avoid having the latest fixes you don't have, you can install the current version of the latest CU.
    Latest updates for Microsoft SQL Server: https://learn.microsoft.com/en-us/sql/database-engine/install-windows/latest-updates-for-microsoft-sql-server?view=sql-server-ver16

    Best regards
    XYJXYJ

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.