Re: Documentation every Database Shop should have

Hi Dennis!

just out of curiosity... what web form tools are you eluding to? I would love to see a very basic app designer tool (ala sorceforge) that would allow this (not htmldb I hope..)

Anything that would replace the 18 xls docs we now use, would be nice

Alsot of the problem with this question is that although we all share the same basic tasks, everyones dept would want it a little different - so unfortunately, excel seems then be the tool of choice ;-)

Thanks
Bob

Dennis Williams wrote:

> David,
>
> My vote is to put all this (maybe not passwords) on a DBA team web
> site (some tools make that easy) so if someone gets called out of bed
> in the middle of the night, they have access to this info, and if they
> are lucky, can electronically search it.
>
> Dennis

-- 
"Oracle error messages being what they are, do not
highlight the correct cause of fault, but will identify
some other error located close to where the real fault lies."

--
http://www.freelists.org/webpage/oracle-l