The change stream is already sequenced.
UOWs are in order by commit timestamp.
Insert/Update/Delete within a UOW are time-sequenced.
DTL__CAPXRESTART1 is a granular sequence if you are running AI (After Image only).
DTL__CAPXRESTART1 + DTL__CAPXACTION combined are a granular sequence if you are running BA (Before and After image).
Thank you Dan...
We are running in AI mode. So, can we use "DTL__CAPXRESTART1" to pick up the latest transactions in case of multiple transactions happened in same commit time? Can it be used as part of the SORTBY?
If you have PWX CDC feeding PC, and PC writing to an RDBMS, then you don't need to do anything special to get that.
Treat source rows as Data Driven, uncheck commit on EOF, and set Recovery Strategy == Resume from last checkpoint.
PC will handle each row based on DTL__CAPXACTION, and data will be properly sequenced.