How to replicate standard ETL jobs in DCC?
When using DCC for data collection, the standard ETL jobs of the CLM applications must be disabled to avoid data corruption.
I need to know: 1) if the DCC jobs fully susbtitute the standard ETL jobs, so that all data that the ETL jobs collect are also collected by the DCC (and stored in the same tables of the DW database); 2) if this is not true, is there an easy way to replicate the standard ETL jobs in DCC? By an export/import process, for example, without manually defining them. I am working with version 5.0.2 of CLM and DCC. |
Accepted answer
Hello Luca,
the burndown report uses the trend data that is stored in the data mart section of the data warehouse. This data is collected every day during the ETL execution and cannot be reconstructed. This means that if you create a new data warehouse, like you did moving from Derby to SQL Server, that historical data is lost. Unluckily there's no way to migrate that data between 2 data warehouse types. You should start seeing good data in the burndown as soon as you start new sprints. Best Regards Francesco Chiossi Luca Martinucci selected this answer as the correct answer
Comments
Luca Martinucci
commented Nov 11 '16, 6:13 a.m.
Francesco,
Francesco Chiossi
commented Nov 11 '16, 6:30 a.m.
Hello Luca,
Luca Martinucci
commented Nov 11 '16, 8:15 a.m.
Thanks for the answer.
|
One other answer
Hello Luca,
the DCC jobs fully replace the default data collection (Java ETL). They collect the same data just in a more efficient way. Make sure however that you have the appropriate resources for DCC as the performance improvement requires extra resources. We recommend to have DCC on a dedicated server, separated from the rest of the CLM applications. Best Regards Francesco Chiossi Comments
Luca Martinucci
commented Nov 11 '16, 4:46 a.m.
Hi Francesco,
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.