Can we change the Task Delay for Data Collection?
![](http://jazz.net/_images/myphoto/5000ef170ac5255f4a978e1f5abefa1f.jpg)
In the Data Warehouse collection configuration for RTC, there is an option for changing the delay of the data collection task. However it says "The time interval in seconds between running this task. Please do not change." We would like to increase the frequency that these data collection jobs run, is this where we would do it, and why does it say not to change it?
2 answers
![](http://jazz.net/_images/myphoto/5000ef170ac5255f4a978e1f5abefa1f.jpg)
What version of RTC? What Data Collection Component?
If you reduce the delay it would potentially put a higher load on your system. That is why it tells you not to change it.
This is dependent on the two questions above and your load and performance of your systems.
If you reduce the delay it would potentially put a higher load on your system. That is why it tells you not to change it.
This is dependent on the two questions above and your load and performance of your systems.
![](http://jazz.net/_images/myphoto/5000ef170ac5255f4a978e1f5abefa1f.jpg)
Hello Stephen,
the default data collection of CLM collects ODS and Metrics in the same execution.
The metrics are designed to get trending data in daily updates, so running it more frequently or less frequently can have adverse effects on the trending data and the data warehouse size.
This is why it's recommended to not change the delay.
If you want to run the ETL on a different schedule, you should use the Data Collection Component (that is optionally available for version 5.0.2).
There you can schedule the ODS and Data Mart parts of the ETL to run on different frequencies as it fits your needs.
Best Regards
Francesco
the default data collection of CLM collects ODS and Metrics in the same execution.
The metrics are designed to get trending data in daily updates, so running it more frequently or less frequently can have adverse effects on the trending data and the data warehouse size.
This is why it's recommended to not change the delay.
If you want to run the ETL on a different schedule, you should use the Data Collection Component (that is optionally available for version 5.0.2).
There you can schedule the ODS and Data Mart parts of the ETL to run on different frequencies as it fits your needs.
Best Regards
Francesco