i've often felt less of a hero, more of a priest. i'd rewrite the 'hero' tip a little:
Tip Number Two: No Priests...
This kills two birds with one stone by giving you first-hand knowledge of the documentable processes and also helps the organization to exorcise its dependency on priests.
the biggest problem you'll have is persuading the rest of the organisation to make the paradigm shift from the roman catholic model to the protestant model.
I found this hilarious! Thanks.
The most difficult DBA of all is the tribal shaman, with secret knowledge no one can ever divine. IMO the DBA should be a champion of good practices within IT, and a vital part of the team. I appreciate you have a lot of work to do; so do we all. I am a Data Architect, and I will tell you, I am NOT a DBA and there are things I don't know! I work on 4 different RDBMS and there is no way I can match the DBA on system specific knowledge. But I am always eager to learn and I need a solid DBA who will make my designs work, and will work with me when they don't.
Can't wait to read the rest.
Kate The Great
If you don't have time to do it right the first time, where will you find time to do it again?