Is there any risk on running the Full Data Collection Job in RRDI?
Jorge Valdeiglesias (54●18●23)
| asked Aug 01 '13, 10:16 a.m.
edited Sep 17 '13, 6:26 a.m. by Krzysztof Kaźmierczyk (7.5k●4●80●103)
We are having an issue with some lost data (never retrieved) in the DWH and the solution in the Sandbox was re running the full ETL. Problem is I've been told that in an older version of RTC you lost some calculated data when you do that.
Question is, is there any risk on running the Full Data Collection Job? Is there any consideration to be taken into account?
|
Accepted answer
Hello Jorge,
the order on which the jobs are executed by the scheduled data collection is the following:
The full data collection jobs can only be started manually. The effect on reports showing historical trends that are calculated during the ETL run will be that, if for example the full ETL will take 1 week to complete, you will only have 1 data point in the report instead of the expected 7. Best Regards, Francesco Jorge Valdeiglesias selected this answer as the correct answer
|
2 other answers
Hello Jorge,
Running full DWH job may take even couple of days, depending on how old your repository is. During that time there are running many SQL queries on RTC database. This might impact your server performance, Best regards, Krzysztof Kazmierczyk |
|
Yes, I imagine it will take a while, but beside that, is there any other consideration? For example, how would you run the jobs? One by one? Or is there an specific order to run them, o maybe a command. And most important, how will this affect the calculated data (for example, now the burndown charts use the time the ETL was run to draw a point in the chart)?
|
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.