Archives of the TeradataForum
Message Posted: Tue, 05 Nov 2002 @ 14:01:07 GMT
Following your description of your security solution, I would like to add that I did a similar thing at a customer quite a while ago, with two differences:
- 'chain' is NOT part of the key, but is referenced in another table
- the user ID's have a fixed structure (known to those assigning them), where two char's indicate the chain ID directly, so there is no need to keep a separate table for permissions (I realize this precludes one user seeing x and only x chains, but this was not a requirement. I did allow for '00' seeing everything.) The nice thing is that this scheme (despite the additional lookup) affects performance very insignificantly.
I did feel strongly about MicroStrategy's precluding the use of database-level security in their version 7, since I believe that security should be at the lowest level possible to reduce maintenance load and security risks. I believe that it will be an option once more in that BI tool...
I did, further back, also implement a similar scheme in Oracle.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 28 Jun 2020|