-Original Message-From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]Sent: Tuesday, December 09, 2003
7:19 PMTo: Multiple recipients of list ORACLE-LSubject:
Re: Documenting databases
The internal stuff can be documented
with OraSnap. Just google for it.
It's free
Alan,
When I started working at my present job there was zip,nada,zilch..
for database documentation. I started with the basics of:
describe every table.
describe the table data source location and provider and method of
loading the data into the table.
describe who or how the data in the table
by:
Subject: Re: Documenting databases
[EMAIL PROTECTED]
.com
:
Sent by: Subject: Re: Documenting
databases
[EMAIL PROTECTED]
.com
12/09/2003 04:09
PM
I used to document database objects (including columns) with the COMMENT
commands. I stopped doing that because I think it unnecessarily increases the
size of data dictionary. It's just a little, though.
Yong Huang
Daniel Hanks wrote:
How about in each database itself.
COMMENT ON TABLE|COLUMN
Alan,
That sounds like a good candidate for a simple database application written
in PL/SQL. Create a schema and model your app. It shouldn't require too many
tables. Since you have Oracle and non-oracle information to store, most of
the Oracle information could be extracted from the data
recipients of list ORACLE-L [EMAIL PROTECTED]
cc:
Subject:Re: Documenting databases
Don't know if this has been mentioned or if it does enough of what you're
looking for but you can pick up something called RDA (remote diagnostic
agent) from Oracle that'll give you an overview of OS
PROTECTED]cc:
orp.com Subject: RE: Re: Documenting databases
Sent
]
Stephane
Faroult To: Multiple recipients of
list ORACLE-L [EMAIL PROTECTED]
[EMAIL PROTECTED]cc:
orp.com Subject: RE: Re: Documenting
databases
Sent
Recently our database manager has asked us to do the unthinkable
document our databases! To make matters worse, and without our input, he
went ahead and created a schema and put it in an Access database (using
tables to make it look like a speadsheet). Either we use his idea or come
On Tue, 9 Dec 2003 [EMAIL PROTECTED] wrote:
Recently our database manager has asked us to do the unthinkable
document our databases! To make matters worse, and without our input, he
went ahead and created a schema and put it in an Access database (using
tables to make it look like a
:
Sent by: Subject: Re: Documenting databases
[EMAIL PROTECTED]
.com
I think you can download a software called DataPublisher from
AgileInfoSoftware, it will automatically document the database for you.
http://www.agileinfosoftware.com/download/products.asp. The output is very
impressive.
Eric
- Original Message -
To: Multiple recipients of list ORACLE-L
PROTECTED]
cc:
Subject:Re: Documenting databases
Dan,
That's a good idea for documenting structures inside the database.
However, my database manager wants more high level info: database name /
host, oracle version, listeners, applications that use it, cron job
descriptions
:34 PM
| Please respond to ORACLE-L
|To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
|cc:
|Subject:Re: Documenting databases
|Dan,
|That's a good idea for documenting structures inside the database.
|However, my database manager wants more
|To: Multiple recipients of list ORACLE-L
[EMAIL PROTECTED]
|cc:
|Subject:Re: Documenting databases
|Dan,
|That's a good idea for documenting structures inside the database.
|However, my database manager wants more high level info: database name
16 matches
Mail list logo
