Gap In Burndown Chart
![]()
During our upgrade process after a few days we noticed the data warehouse was not getting updated after the upgrade.
The upgrade was done on July 9th. And we restored the DCC and data warehouse jobs on July 20th. On our burndown charts we noticed the gap in data from July 9th to July 20th. We changed the 'Delta Load Configuration' to July 8th. Thinking this would grab data from July 8th through today.
The jobs ran successfully and the ETL logs show that it was attempting to get changes since July 8th. Any ideas as to why we still have the gap in data?
|
Be the first one to answer this question!
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.
Comments
Do the Data Warehouse Jobs need to run every night to pick up Burndown data? Or can they be run to 'catch up' on failed runs? For Example using the 'Delta Load Configuration' to pick a date when it last ran successfully.
So according to this article...
So, if the data warehouse jobs don't run for a couple of days or fail. Then there would be no data in the burndown chart for those days and there is no way to get those back dated events?