C
carloscefs
Guest
ADP is implementing CDC and Pro2 for ADP’s biggest customer where they handle over 100 million transactions per day. One specific table have approximately 40 million transactions per day as well. There was a need to maintain CDC working and one of the actions was to purge all CDC data. For this database we identified 2 billion CDC changes in the queue. For another pre-production environment we deployed the latest pro2 hotfix 5043 version and then a purge was needed one more time for this database. Again, we were not able to truncate CDC due to OE restrictions. error message - Area cannot be truncated because it contains the CDC Change Tracking table (18467) The only alternative was to run a "for each delete" for all records - in order to achieve it, ADP had to start 15 threads and it took 10 days to purge all data, impacting our production implementation severely. The database in question is used for Human Resources with over 150000 employees. This massive record delete, also cause a performance issue (known defect), impacting day by day usage. A simple count on CDC table took around 40 minutes to return 0 records. IDXBUILD on CDC area fix this issue. If DBAs can truncate CDC area our implementation and administration could be more efficient and productive rather than to wait days to simply delete records. Please review and consider this enhancement request as it will be beneficial to ADP and all customers using CDC with or without Pro2. Regards, ADP team.
Continue reading...
Continue reading...