A Toad® for Oracle Case Study, by Michael Allen
(from the Cascading Chaos and Risk Due to Corrupt Data series)
All reports are suspect from a database corrupted with leading spaces. Errors caused by leading spaces can vary from insignificant to catastrophic. Consequences depend upon the volume of corruption, the significance of the columns corrupted, and how each individual report or chart uses those corrupted values. Only a detailed, time consuming - and therefore costly - manual analysis of each report or chart can determine with a reasonable degree of certainty the impact on the results.
This case study illustrates how Quest’s Toad for Oracle tool provides an easy-to-use, intuitive set of capabilities to prevent data corruption with a leading space and how to enable the information owner for simple purification of data already corrupted.