Monday morning data problems - lessons learned

[Daniel_Dukes]

Share one story where a dashboard, model, pipeline, or report looked correct on Friday but broke by Monday. What was the hidden root cause (master data mismatch, late arriving data, access change, schema change, governance gap)? What rule or check did you put in place so it would not happen again?

Keep it short: problem, impact, fix, and one lesson learned.

[Martin_Kuma]

Problem: SAC Stories: table widget -> Sort order of Measures changed (after SAC Update / behavior change)

Impact: user experience 

fix: workaround, slowing down SAC Story, but solving the sort order problem 

lesson learned: the only constant is the change

not sure if this is what you expected 🙂

[Daniel_Dukes]

Hi Martin,

Thanks for sharing and contributing to the community!

My story speaks to self-affliction 🙂 One Friday evening I had one last step to finish a project. Rushing to get home, I moved a secondary index to production on one of SAP's largest tables without informing our basis/dba team. I got a "nice call" that weekend after all our jobs canceled due to no disk storage space. Monday morning everyone was cleaning up the fallout. Moving forward, we worked towards better communication between teams along with coordinated go-live planning. Definitely a growth experience for me as a data professional.

[Martin_Kuma]

oh, got it Daniel :). Been there as well, but I made a mistake in BW - Transformation mapping. Mixed GUIDs from PDM source system. I was doing the change as an emergency on production... The result of the staging was used for an external DB table, which got out of space as well. This was not on Friday, but lesson learned: doing emergency changes at the end of a day, tired, is not a good idea 🙂