RogerCruse
MIS
Hi,
Currently, all access rights use the standard USER / DATABASE model and I want to migrate to a ROLE / DATABASE model now possible with V2R5.
This should reduce the overall size of dbc.accessrights and reduce LOCKS occuring plus greatly simplify the administration process.
Has anybody done this?
What issues are there and how did you resolve them?
So far, to test my understanding of Roles within Teradata I've created a couple of userids and assigned them a Role and granted this Role access to a database.
e.g.
CREATE ROLE ROLE_TEST1;
GRANT SELECT ON DATABASE_TEST1 TO ROLE_TEST1;
GRANT ROLE_TEST1 TO USER1;
But when I test it - getting USER1 to access a table in DATABASE_TEST1 - it fails. If I give USER1 access directly, it works.
What have I missed?
Is there something NCR need to enable?
Roger...
Currently, all access rights use the standard USER / DATABASE model and I want to migrate to a ROLE / DATABASE model now possible with V2R5.
This should reduce the overall size of dbc.accessrights and reduce LOCKS occuring plus greatly simplify the administration process.
Has anybody done this?
What issues are there and how did you resolve them?
So far, to test my understanding of Roles within Teradata I've created a couple of userids and assigned them a Role and granted this Role access to a database.
e.g.
CREATE ROLE ROLE_TEST1;
GRANT SELECT ON DATABASE_TEST1 TO ROLE_TEST1;
GRANT ROLE_TEST1 TO USER1;
But when I test it - getting USER1 to access a table in DATABASE_TEST1 - it fails. If I give USER1 access directly, it works.
What have I missed?
Is there something NCR need to enable?
Roger...