Archives of the TeradataForum
Message Posted: Wed, 24 Oct 2012 @ 20:36:47 GMT
This is an issue with Teradata Client tools.
I am providing the use case so that you can get a more complete picture:
Customer A is sharing a Teradata box with 3 other customers and Customer A is using Teradata Studio as a client tool and when he logs on, he is actually able to see all the databases and tables of other customers.
Usually the DBC tree is built by the Teradata PUBLIC user by accessing DBC.Tables , DBC.Databases and DBC.Columns. Is there a way that we revoke access to DBC from public and make the JDBC connection ( Teradata studio) point at ?something else? ?and built the tree , so that the customer A does not get an indication that there are other customers on the Teradata box.
I tried to grant access to DBC.Xviews to PUBLIC and revoked access to DBC from PUBLIC and tried to create a user. It did limit the tree view to the databases that the user had access to, however I was not able to drill into the tree, which would again cause issue.
However when I try the same on the SQL Assistant , then it perfectly works. I revoke access to DBC form PUBLIC and grant to XViews, then the customer can just see his views and databases and not others without any issue.
Could anyone give me any clue/ thought as to any kind of solution for the issue.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|