Hai,
Can anyone tell me how to catch catch the deleted records while performing CDC(Change Data Capture)
CAPTURING THE DELETEDRECORDS...............
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 9
- Joined: Sat Mar 18, 2006 1:53 pm
-
- Premium Member
- Posts: 397
- Joined: Wed Apr 12, 2006 2:28 pm
- Location: Tennesse
It seems he is on Server and means the CDD technique and not the stage (as available in EE). Akansa, in order that the deleted rows are accounted for, you will have to maintain an image of the previous load. Only then will you be able to do what you were asking for. There was a job design that was posted here some time back which dealt with this, interestingly; but I just could not find it.
gateleys
gateleys
-
- Participant
- Posts: 9
- Joined: Sat Mar 18, 2006 1:53 pm
To capture records from target table which are no longer present in the source you can do the following:
Read all the Keys from the Target. This is your primary input. Load all the keys from the source in the hashed file and use that as lookup. Now bring out only those rows from your target which don't have a match in your hashed file and set your update action as "Delete existing rows" and that will delete all the records in the target. Now to capture them, just write those rows to a sequential file instead of deleting. It's upto your requirement.
IHTH
Read all the Keys from the Target. This is your primary input. Load all the keys from the source in the hashed file and use that as lookup. Now bring out only those rows from your target which don't have a match in your hashed file and set your update action as "Delete existing rows" and that will delete all the records in the target. Now to capture them, just write those rows to a sequential file instead of deleting. It's upto your requirement.
IHTH
Kris
Where's the "Any" key?-Homer Simpson
Where's the "Any" key?-Homer Simpson