"Well, about six months into operation of this ERP Holden heard his boss start to repeatedly mutter "Oh god" in an increasingly panicked tone. "His face had turned an interesting shade of puce and he looked a little uncomfortable," Holden wrote. "It transpired he'd accidentally wiped a key piece of data from our expense transactions which left them all in a hung state and unable to be processed." Holden found a shadow table that made it possible to reconstruct the missing data."
"Two months later another team member approached the boss's desk and admitted to "a bit of a problem - I've accidentally deleted some relations." He'd actually deleted them all. While constructing a complex query, he dropped the main relational table for the general ledger. "This necessitated a company-wide 'The ERP is down for emergency maintenance' notification, and a rapid restore from the previous evening's backup," Holden told Who, Me?"
An organization implemented a managed-build ERP that overran by 12 months, resulting in a buggy system lacking advanced reporting. Staff accessed the database directly via SQL to extract complex reports. Six months after go-live, a manager accidentally wiped a key data piece from expense transactions, leaving them hung and unprocessable; recovery came from a shadow table. Two months later, another team member accidentally dropped the main relational general ledger table while crafting a complex query, necessitating an emergency company-wide outage and restoration from the previous evening's backup. The incidents prompted the company to issue strict procedural instructions to the team.
Read at Theregister
Unable to calculate read time
Collection
[
|
...
]