November 20, 2013 at 9:47 am
Hello everyone,
We have a vendor that wants us to run a SQL script on our server. One example within the script:
USE[master]
GO
GRANT EXECUTE ON[sys].[sp_OASetProperty] TO[public]
GO
It includes sp_oasetproperty, sp_OAMethod, sp_OAGetErrorInfo, sp_OADestroy, sp_OAStop, sp_OACreate, sp_OAGetProperty, sp_configure'show advanced options',1 ; and sp_configure'Ole Automation Procedures',1.
My own Googling shows these stored procedures work with the COM object. It was requested I run this script against the master database using a SA account (it's mapped to a few user databases). While that's fine, we have over 30 user databases on this server.
Do I have a concern executing this script? We need to ensure there's no impact to the other databases. Any comments / URLs are appreciated - thanks.
November 20, 2013 at 9:53 am
not to public.
if they need to run sp_Oa*, then only grant it to one specificl role or user/login that will actually need and use it.
depending on what they are actually doing, there probably exists a CLR stored procedure, already out there, to do the same work, but that would require them to change their code to use CLR instead of sp_OaCreate calls(leftover SQL2000 code?)
Lowell
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply