RE: SELECT Permissions on Schemas
- From: Erland Sommarskog <esquel@xxxxxxxxxxxxx>
- Date: Tue, 3 Jul 2007 19:47:21 +0000 (UTC)
Todd C (ToddC@xxxxxxxxxxxxxxxxxxxxxxxxx) writes:
It just seems messy when dealing with ODBC connections because those
views exist in the Master Database (to which the user is NOT listed as a
login), yet he sees all 250+ system objects listed when he goes to link
a table in a user database.
So your real problem is that the objects in the master database deluge
what the user sees in Access? Why Access lists everything in sight I don't
know.
I believe that master has the guest user enabled, and you cannot turn that
off.
"You want to access table X? Then I need to know which columns there
are".
The better approach might have been: "OK, you want access to Table X, then
the system and NOT the USER will go query the meta table to determine
structure.
Unfortunately that does not fly. It is the API that asks this question
and send down the metadata query. And the API can only work with the
user's authentication.
--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
.
- References:
- RE: SELECT Permissions on Schemas
- From: Erland Sommarskog
- RE: SELECT Permissions on Schemas
- Prev by Date: RE: SELECT Permissions on Schemas
- Next by Date: Re: Master Key Issue
- Previous by thread: RE: SELECT Permissions on Schemas
- Next by thread: Re: Master Key Issue
- Index(es):
Relevant Pages
|
