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.
Not that every company will have this kind of sensitivity but if I had done that in the past, the company would have been out of business for being sued because the CIO was also a DA (and that's not a legal term in this case). 😉 Sometimes you have to protect the officers from themselves. :hehe:
--Jeff Moden
Change is inevitable... Change for the better is not.