Difference between revisions of "Db-edit"

From dbscript Online Help
Jump to: navigation, search
(MSSQL Server database properties)
Line 9: Line 9:
 
The user must have read access to the meta data, either  
 
The user must have read access to the meta data, either  
  
- being db_owner in the database, or  
+
* being db_owner in the database, or  
- having at the VIEW DEFINITION grant
+
* having at the VIEW DEFINITION grant
  
 
=== Oracle database properties ===
 
=== Oracle database properties ===

Revision as of 14:50, 27 October 2012

Online Documentation for dbscript by devio

Display and edit Database properties.

MSSQL Server database properties

Server, Catalog, Username and Password must be provided for live database.

The user must have read access to the meta data, either

  • being db_owner in the database, or
  • having at the VIEW DEFINITION grant

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.

Documenting Oracle Databases in dbscript

Connections

If all required fields are entered, press the "Test Connection" button to test whether the settings are correct, and dbscript can access the database.

If the connection test succeeds, the "Can Connect" field is checked. Otherwise, an error message is displayed.

Note that the target database is accessed from the web server, not from the client machine.