Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

sys.xp_prop_oledb_provider Expand / Collapse
Author
Message
Posted Thursday, February 5, 2009 8:23 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Friday, May 17, 2013 4:02 PM
Points: 51, Visits: 290
Hello,

Can you explain me what are the consequences of granting users this permission:

GRANT EXECUTE ON sys.xp_prop_oledb_provider TO [USER]

I gave it to users in order to let him see Linked Servers Catalogs. Now I wonder it that is the only change of his permissions or does he get also something "extra" without my knowledge.

Post #650922
Posted Thursday, October 29, 2009 6:45 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Wednesday, September 11, 2013 1:41 AM
Points: 62, Visits: 195
I have a problem in adding a linked server from sql 2005x64 to oracle.
I have created the linked server

EXEC sp_addlinkedserver
@server = 'job',
@srvproduct = 'Oracle',
@provider = 'OraOLEDB.Oracle',
@datasrc = 'tns'

and added a login

sp_addlinkedsrvlogin @rmtsrvname = 'job'
, @useself = 'false'
, @locallogin = 'opTrasp'
, @rmtuser = 'remUs'
, @rmtpassword = 'pwd'

but I have the error
The EXECUTE permission was denied on the object 'xp_prop_oledb_provider', database 'mssqlsystemresource', schema 'sys'. (Microsoft SQL Server, Error: 229)

in the test server, running sql 2000 instead of sql 2005) it worked without assigning any further permission to the local login.
Is it necessary? and is it 'dangerous', considering that it is a cluster with many critical databases of different suppliers?

Thanks in advance for your kind replies.
sb
Post #810704
Posted Wednesday, May 19, 2010 10:39 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, July 24, 2014 12:52 PM
Points: 5, Visits: 105
I also needed to know what "xp_prop_oledb_provider" is all about? Can anyone help?

Are we granting another access to the user when we grant them additional execute permission in this procedure?
Post #924497
Posted Thursday, December 16, 2010 8:19 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, December 16, 2010 8:18 AM
Points: 1, Visits: 0
revisa este link

http://blogs.msdn.com/b/john_daskalakis/archive/2010/02/01/9956271.aspx

por ahi te dejo lo mas importante.

USE master;
Grant execute on sys.xp_prop_oledb_provider to login;
GO

(replace login with the actual login you are using that gets this error)

Post #1035873
Posted Monday, November 25, 2013 1:38 PM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Saturday, June 28, 2014 8:50 AM
Points: 2,649, Visits: 766
In my situation, we had a linked server that was accessed from the reports. The database had the correct permission through a linked server, the account that the reports used had the right permission, but the linked server was not setup to allow the report account through (the linked server). Once that account was added with impersonation to the linked server, the error went away.

Jamie
Post #1517447
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse