Change Data Capture(CDC) when running Batch jobs
Page 1 of 1
Change Data Capture(CDC) when running Batch jobs
Hi
As we know, when the CDC is running any changes in the data will be recorded. Also we know batch jobs(with many transactions) can executed several times a day and caused many changes in data(for example, in banking industry ).
My question is that when changes are recorded if a batch job is executed, is this creates a lot of false alarms?
The CDC must be switched off during executing batch jobs??????
How can we distinguish between these two(changed arise from batch job (that are normal changes) and other changes(that may be suspicious))???
Thanks
As we know, when the CDC is running any changes in the data will be recorded. Also we know batch jobs(with many transactions) can executed several times a day and caused many changes in data(for example, in banking industry ).
My question is that when changes are recorded if a batch job is executed, is this creates a lot of false alarms?
The CDC must be switched off during executing batch jobs??????
How can we distinguish between these two(changed arise from batch job (that are normal changes) and other changes(that may be suspicious))???
Thanks
tosan.tidm- Posts : 1
Join date : 2014-04-17
Re: Change Data Capture(CDC) when running Batch jobs
1. Configure your CDC process so it only captures data changes you are interested in
2. The files generated by the CDC process contain only potential changes - you can still implement logic in your ETL process to decide whether or not to updates your DW with a record in a CDC file/table
2. The files generated by the CDC process contain only potential changes - you can still implement logic in your ETL process to decide whether or not to updates your DW with a record in a CDC file/table
nick_white- Posts : 364
Join date : 2014-01-06
Location : London
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum
|
|