Re: SQL 2005, sysobjects and security
- From: Erland Sommarskog <esquel@xxxxxxxxxxxxx>
- Date: Sun, 16 Sep 2007 22:14:02 +0000 (UTC)
Marius Horak (nobody@xxxxxx) writes:
Erland Sommarskog wrote:
So when you say that sa can't access sysobjects, I need to ask how you
have arrived at this conclusion
This is elementary Dr.Watson.
If you cannot see it, you cannot access it.
The reporting tool displays nasty message - "Table X has no columns."
That is the message to expect when running a query against sysobjects
and syscolumns from a low-priv user in SQL 2005. That is the query runs,
but no data is returned.
For sa the query should still return data.
--
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
.
- Follow-Ups:
- Re: SQL 2005, sysobjects and security
- From: Marius Horak
- Re: SQL 2005, sysobjects and security
- References:
- SQL 2005, sysobjects and security
- From: Marius Horak
- Re: SQL 2005, sysobjects and security
- From: Erland Sommarskog
- Re: SQL 2005, sysobjects and security
- From: Marius Horak
- SQL 2005, sysobjects and security
- Prev by Date: Re: SQL 2005, sysobjects and security
- Next by Date: Re: Query/View Privileges
- Previous by thread: Re: SQL 2005, sysobjects and security
- Next by thread: Re: SQL 2005, sysobjects and security
- Index(es):
Relevant Pages
|
|