F
fabio.medina
Guest
ADP is implementing CDC and Pro2 for ADP’s biggest customer where they handle over 100 million transactions per day. One specific table has approximately 40 million transactions per day. There was a need to maintain CDC working and one of the actions was to purge all CDC data. For this database ADP has identified 2 billion CDC changes in the queue, because when ADP first implemented CDC with Pro2 ADP team indentifed that CDCBatch.bat has a disposition parameter that needs to be changed from APPLIED to DELETE, so it deletes records instead of marking them as applied. Business Impact: 1. The replication was not working as fast as it should. 2. Delay on implementing the new solution to the biggest ADP's customer (GPA) 3. Administration tasks for DBs took long times in order to maintain all the areas and the records clean, Backup, restore, etc. 4. Extremiley poor peformance for all programs that use this DB where the CDCBatch was running. Workaround: 1. Manually change the CDCBatch.bat from APPLIED to DELETE. 2. Perform maintenance to the environment by purging the CDC records otherwise it's going to do table scan for each change into _cdc-change-tracking. It has been extremelly painful to ADP and its customer (GAP) to not have the new solution in place as well as the poor peformance of the product. Please review and consider this enhancement request as it will be beneficial to ADP and all customers using CDC with or without Pro2. ADP Team
Continue reading...
Continue reading...