2

I'm using CDC feature to track changes that are being made, since the cleanup period is set to 3 days by default, I have to run jobs to archive this change data from the CDC system tables to my tables. However, there's a probability that CDC might delete a few change data records that I haven't been able to archive yet.

For instance, if i set the retention period to 10 minutes and run the cleanup job after 10 minutes, only the data that has been archived should be deleted, and the data that hasn't been archived should be left untouched. Is there a way around this predicament?

  • Can't you make sure that you always archive and empty well before (and I'm talking at least hours) the retention period expires? – James Anderson Aug 26 '15 at 10:12
  • Yea, that is one option, but if something goes wrong and you're unable to archive it, I want to be sure that I won't lose the unprocessed data – Ritesh Bhakre Aug 26 '15 at 11:20
  • 1
    How long could something be wrong before you or clients would notice? Make the expiry time twice that. – James Anderson Aug 26 '15 at 12:44
  • Yes...you could disable the job and roll your own. But no, if you want to use what is created when you enable CDC. – Steve Mangiameli Sep 2 '15 at 19:18

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.