Change Data Capture as a long-term change-tracking solution

  • Has anyone used CDC as a long-term solution for change-tracking? It seems to me as though this was not intended as a platform to be used to capture and retain changes for longer than a few days. I'm very concerned that it would start becoming unmanageable/unsearchable before too long, unless you were regularly flushing the data out to a user table.

  • Yeah, it wasn't intended to be used that way, so my guess is it wouldn't work all that well for that. Even performance could become a real issue at some point.

    You'd likely be better off creating archive tables and using those.

    SQL DBA,SQL Server MVP(07, 08, 09) "It's a dog-eat-dog world, and I'm wearing Milk-Bone underwear." "Norm", on "Cheers". Also from "Cheers", from "Carla": "You need to know 3 things about Tortelli men: Tortelli men draw women like flies; Tortelli men treat women like flies; Tortelli men's brains are in their flies".

  • It is only meant to be used for very short term storage of the data, maybe 2-3 days.

    I believe the default retention is 3 days.

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply