Here is more detail on the current issue
1.Run the profiling on SQL server without enabling Incremental profiling. 23 tables present in DB and 23 tables sent for profiling
2.The second run added 2 more tables and selected Incremental Profiling
Now ideally the expectation is to have 2 tables sent for profiling. But we see 25 tables sent for profiling.
We see 25 logs created in $INFA_HOME/ logs/node01/services/DataIntegrationService/disLogs/profiling which confirms incremental profiling is not working
Not honoring Support
Thanks for the explanation. Assuming this were working and going back to my original question, how would it identify the two that needed to be scanned. Just trying to understand where the load would be in terms of performance as our DBAs already have some concerns about the performance hit on the source SQL servers with the initial loads. We were hoping that incremental profiling would alleviate some of that concern.
This not working seems to be a pretty big issue. Is there any type of ETA on when this will be addressed?