Archives of the TeradataForum
Message Posted: Fri, 04 May 2001 @ 17:12:54 GMT
I'm getting really confused here. BI/Query has the capability to limit the scope of a person's access based completely in the model itself, both what they see on the model and through more complex ways that can be specified on the user level. In addition, metadata can be stored in separate tables for BI/Query only, if you really (Lord knows why) need to limit access to DBC.Tables, Columns, other views, etc. (Time for a short commercial: Len Gavin of Integris is developing a tool that extracts data from the Teradata MDS and load that into the appropriate BI/Query tables. We now return to your usual programming). But why limit access to those DBC views anyway? They tell you ABSOLUTELY NOTHING about users or their capabilities. How about the DBC "X" views, which limit things to only those areas you have access to? Come on, there has to be another way then locking down DBC views as a general rule.
Frank C. Martinez IV
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|