|
Archives of the TeradataForumMessage Posted: Fri, 04 May 2001 @ 15:11:38 GMT
Hi, I don't think that upgrading Teradata, the ODBC driver etc will change this, but I think it unlikely that you've got an issue (unless your security/audit rules are particularly strict). Most ODBC-based tools that I've come across ask for data from the "system catalog" - database dbc in Teradata's case. The NCR ODBC driver maps the standard odbc catalog access requests to selects run against the standard views defined in database dbc, things like dbc.tables, dbc.columns etc. Most userid's on most Teradata sites allow read access to these views, in fact the standard Teradata install grants SELECT to PUBLIC on these views. If you give some specific examples of what your concerns are then maybe I can give you ideas as to how to avoid them. Cheers, Dave
| ||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||
Copyright 2016 - All Rights Reserved | ||||||||||||||||||||||||||||||||||||||||||||||||
Last Modified: 15 Jun 2023 | ||||||||||||||||||||||||||||||||||||||||||||||||