joel.weiss 70857 (7/6/2010)
I agree with your mentor up to a point, and this is a critical point: a DBA, by definition, is an administrator, not an officer. Seeking out data and judging whether it is critical, real or worth saving is not part of the job. Overdoing this role contains an inherent risk of creating unnecessary infrastructure and producting redundant data, which is a different type of risk (accuracy). Leave those judgement calls to the CIO.
From the CIOs I've seen, this kind of concern is something they'd delegate at best. They have their minds on other things and in many cases either don't have the time for this kind of low-level activity or simply don't have the expertise needed.
--------------------------------------
When you encounter a problem, if the solution isn't readily evident go back to the start and check your assumptions.
--------------------------------------
It’s unpleasantly like being drunk.
What’s so unpleasant about being drunk?
You ask a glass of water. -- Douglas Adams