Re: INSERT Permission & Linked Servers
- From: Erland Sommarskog <esquel@xxxxxxxxxxxxx>
- Date: Mon, 14 Jan 2008 14:56:14 -0800
Craig Wagner (MSDNNospam207@xxxxxxxxxxxxx) writes:
We are in the process of upgrading from SQL2000 to SQL2005. We
discovered one odd behavior in our testing and I've been unable to
determine if this is by design.
We have two servers (A and B). A table (X) exists in a database on
server A. A stored procedure on server B is executed that inserts data
into table X. The account executing the stored procedure has been
granted INSERT to table X.
In SQL2000 this worked just fine. In SQL2005 it generates an error:
Msg 7357, Level 16, State 2, Line 1
Cannot process the object ""Sample"."dbo"."sampletable"". The OLE DB
provider "SQLNCLI" for linked server "sample_svr" indicates that either
the object has no columns or the current user does not have permissions
on that object.
If I grant SELECT permission on the table then the INSERT works.
I would suspecct that this is due to change in how metadata is exposed.
In SQL 2000 everyone has access to metadata. In SQL 2005 you can only
see metadata for an object if you have the permission VIEW DEFINITION
on that object. This permission is implied if you have SELECT permission,
but it appears that INSERT does not imply this permission.
So try granting VIEW DEFINITION rather than INSERT and see if that works
better.
--
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: INSERT Permission & Linked Servers
- From: Craig Wagner
- Re: INSERT Permission & Linked Servers
- Prev by Date: Re: The signature of the public key is invalid
- Next by Date: Re: INSERT Permission & Linked Servers
- Previous by thread: Re: SQL Agent Jobs - Permissions
- Next by thread: Re: INSERT Permission & Linked Servers
- Index(es):
Relevant Pages
|
|