Difference between revisions of "Db-edit"
(New page: {{Template:dbsweb}}) |
|||
| Line 1: | Line 1: | ||
{{Template:dbsweb}} | {{Template:dbsweb}} | ||
| + | |||
| + | === MSSQL Server database properties === | ||
| + | |||
| + | Server, Catalog, Username and Password must be provided for live database. | ||
| + | |||
| + | === Oracle database properties === | ||
| + | |||
| + | You can define the Oracle connection in two ways: | ||
| + | |||
| + | * set “Server” to the instance name listed inside tnsnames.ora and leave “Catalog” empty | ||
| + | * set “Server” to server:port, and “Catalog” to the service name (as in tnsnames.ora) | ||
| + | |||
| + | A new field called “Import Options” allows you to define the scope of the schema import: | ||
| + | |||
| + | * “USER” (the default value) | ||
| + | * “ALL:” + list of user names | ||
| + | * “DBA:” + list of user names | ||
| + | |||
| + | The user specified in “Username” needs to have access to the ALL_ and DBA_ catalog views, respectively. | ||
| + | |||
| + | [http://devio.wordpress.com/2009/06/10/documenting-oracle-databases/ Documenting Oracle Databases in dbscript] | ||
Revision as of 22:38, 10 June 2009
| Online Documentation for dbscript by devio |
MSSQL Server database properties
Server, Catalog, Username and Password must be provided for live database.
Oracle database properties
You can define the Oracle connection in two ways:
* set “Server” to the instance name listed inside tnsnames.ora and leave “Catalog” empty * set “Server” to server:port, and “Catalog” to the service name (as in tnsnames.ora)
A new field called “Import Options” allows you to define the scope of the schema import:
* “USER” (the default value) * “ALL:” + list of user names * “DBA:” + list of user names
The user specified in “Username” needs to have access to the ALL_ and DBA_ catalog views, respectively.
