Users

From DBArtisan
Jump to: navigation, search

Go Up to Supported Objects

A user is an individual with access to the DBMS.

Creating and editing

Note: Creation and editing of objects of this type is not supported against Sybase IQ datasources.

DBMS platform availability and object actions/operations supported

The following table lists object actions available for this object type. For an introduction to object actions and details on usage of specific actions, see Object actions.

DB2 LUW DB2 z/OS MySQL ORCL SQL SVR SYB ASE SYB ASE

Analyze

Change Password

Compile

Create Like

Drop

Extract

Hide Text

Migrate

Report

Transfer Ownership

Navigator/Explorer Details

Depending on the DBMS platform, the icon associated with a user differs according to the account’s locked or unlocked state, when viewed in the Navigator/Explorer.

DBMS Platform Icon User Accont State

ORCL or SYB IQ

ap240dc5.jpg

Locked

ap240dcf.jpg

Unlocked

IBM DB2 for Linux, Unix, and Windows Users

IBM DB2 for Linux, Unix, and Windows relies on your machine’s operating system to define users for the server. You create and maintain users through your operating system.

Note: DBArtisan lets you set a default SQLID user for a DB2 data source. This lets the user set the implicit schema for the unqualified object references to a schema different from the user's login id.

IBM DB2 for OS/390 and z/OS Users

IBM DB2 relies on the operating system you are running to define users for the server. This means that users are created and maintained through your operating system.

Note: DBArtisan lets you set a default SCHEMA user for a DB2 data source. This lets the user set the implicit schema for the unqualified object references to a schema different from the user's login id.

Microsoft SQL Server Users

Microsoft SQL Server controls access at the database level by requiring the System Administrator or Database Owner to add a login as a database user or alias. After you create a database user, you can implement further security by the granting or revoking the privileges for that user on specific database objects. To consolidate the process of granting or revoking permissions to many users, the database owner can assign users to groups.

MySQL Users

Unlike adding new users to other platforms, MySQL doesn’t rely solely on a userid/password combination. The MySQL server must not only validate the user and password, but also the host from which the connection is being requested before the new user is admitted to the server’s inner sanctum. The User Wizard and User Editor enable these validations.

Oracle Users

To access an Oracle database, you need a user account authenticated with a password. A user account is what Oracle uses to permit access by the user. You can assign the following optional properties to the user:

  • Default tablespace
  • Temporary tablespace
  • Quotas for allocating space in tablespaces
  • Profile containing resource limits

Sybase ASE Users

Sybase ASE controls access at the database level by requiring the System Administrator or Database Owner to add a login as a database user or alias. After you create a database user, you can implement further security by granting or revoking the privileges for that user on specific database objects. To consolidate the process of granting or revoking permissions to many users, the database owner can assign users to groups.