Sprinzing, Thomas wrote: > > Hi there, > is there any way of hiding the system tables or moving them > to some other > namespace? > > I have a third party application here, that makes use of a > table called > Messages. I created a user ts, and was able to set up the > table messages for > ts. however, if the Software connects via odbc, it seems to > see the system > messages table, which is not the desired one...
Just to check: you did a connect as user ts, then did a create table messages, did a commit (or did you miss that ?!), your software connects as user ts (or another one?) and cannot see its own table messages? Which tables does a new connect via SQLStudio see for user ts? Explanation: if one has no table/view/synonym named X, it is used in a small hierarchy including the sysdba. If you have an own table/view/synonym named X, this will hide the sysdba.messages if specified without <owner>. With sysdba.messages the systemtable can be reached even if an own table messages exist. If user ts created a table X, the user ty will not see it even if he was granted some privileges for it unless the user ty prefixes the table X from user ts with ts--> ts.X. Elke SAP Labs Berlin _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
