Re: SQL 2005, sysobjects and security
- From: Erland Sommarskog <esquel@xxxxxxxxxxxxx>
- Date: Sun, 16 Sep 2007 10:15:43 +0000 (UTC)
Marius Horak (nobody@xxxxxx) writes:
We have a reporting tool that needs to access sysobjects.
This tool is used by most of our users but now it does not work on SQL
Server 2005 as the security is different. Not even sa can see
sysobjects. What should I do to allow sa (or any other user) to access
sysobjects?
Security is indeed different. Users no longer see all metadata by default,
only to objects they have access to.
If you users need to acecss metadata through the reporting tool, you
can address with this command
GRANT VIEW DEFINITION TO <user>
Where <user> can be an individual user, a role or "public" to include
everyone, just as you see fit.
All users can still access sysobjects, which no longer is a table, but a
compatibility view. The new system tables are indeed invisible to everyone,
including sa.
So when you say that sa can't access sysobjects, I need to ask how you
have arrived at this conclusion, and particular what error messages you
see, as well which commands that yielded those messages.
--
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
- SQL 2005, sysobjects and security
- Prev by Date: Re: Trusted SQL Server connection (SQL 2005)
- Next by Date: Re: Authentication options with SS2005
- Previous by thread: SQL 2005, sysobjects and security
- Next by thread: Re: SQL 2005, sysobjects and security
- Index(es):
Relevant Pages
|
