You can use the Authorization editor to make an association between a database user and an OS server user ID in a Teradata physical model. Using the authorization feature, you can let an external routine run in a secured mode using the context, permissions, and access control given to the specified OS user.
In Teradata, objects are owned by databases or users. A database and a user are equivalent with the exception that only a user can login to the database. A database or a user can act as a schema.
Note: Passwords will not be stored, but you can use a UDP to generate a password for forward engineering.
To authorize Teradata database users
The Authorization Editor opens.
Note: Click New on the toolbar to create a new authorization. Use the Enter filter text text box to filter a very large list of authorizations to quickly locate the one you want to work with.
Specifies the name of the available authorizations.
Specifies the type of authorization. Select the type from the drop-down list. Valid options are: Definer, Definer Default, and Invoker.
Specifies the schema of the database to which the table belongs. Select from the drop-down list.
Lets you select whether Forward Engineering will use the REPLACE command instead of the CREATE command.
Generates DDL for this object during Forward Engineering.
Specifies the domain name for the OS user.
Specifies the OS user.
The Authorization Editor closes.
Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |