Archives of the TeradataForum

Message Posted: Thu, 14 Oct 2010 @ 15:57:38 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

Try GRANT CHECKPOINT at the database level for any database containing DDL you want to expose. If you need to control access to DDL object-by- object, I think you'd have to write a view DDL from dbc.tables, dbc.columns, etc. If you're doing it that way, you could probably come up with some summary info that might be sufficient - maybe just listing the PI for each table along with any S- or JIs, partitioning, etc.

Regarding the question of exposing DDL somehow breaking the abstraction function of views, I'd say it does no such thing. Whether or not you know how a view is assembled, the data is still abstracted from its source tables. As somebody who spends a lot of time writing queries, it would be far, far harder to do what I do without being able to see the full set of transformations my output comes from. I think that's true for any RDBMS, but TD has the extra consideration that query performance is strongly tied to physical design. If people writing queries can't see the underlying physical structure they're writing against, they'll never be able to write efficient queries.

Dave

	<Prev	Next>		<<First	<Prev	Next>	Last>>