Blocking Stored Procedures

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2005 » SQL Server 2005 General Discussion » Blocking Stored Procedures

Blocking Stored Procedures

Rate Topic

Display Mode

Topic Options

Author

Message

cindy.hutchins

Posted Friday, September 18, 2009 9:19 AM

Grasshopper

Group: General Forum Members
Last Login: Monday, September 21, 2009 7:34 AM
Points: 17, Visits: 21

Our company has had many consultants come in over the last few years and apparently one of them wrote a stored procedure that hasn't been run since 06. How can I block access to keep anyone from running this stored procedure again.

Post #790468

Tommy Bollhofer

Posted Friday, September 18, 2009 9:37 AM

Ten Centuries

Group: General Forum Members
Last Login: Thursday, May 16, 2013 12:43 PM
Points: 1,148, Visits: 3,148

cindy.hutchins (9/18/2009)

i.e.

DENY EXECUTE,VIEW DEFINITION ON usp_MyProc TO SomeDatabaseRole

Tommy

Post #790494

Carleton

Posted Friday, September 18, 2009 11:59 PM

SSC-Enthusiastic

Group: General Forum Members
Last Login: Friday, June 08, 2012 12:30 AM
Points: 150, Visits: 3,892

If your pretty sure this procedure is not needed anymore and it is a security risk, you probably should drop it:

DROP PROCEDURE [ProcedureName]

Post #790751

arun.sas

Posted Saturday, September 19, 2009 12:17 AM

Ten Centuries

Group: General Forum Members
Last Login: Thursday, April 19, 2012 10:25 PM
Points: 1,231, Visits: 3,483

More safe is making a return statement with desired messages in the SP,then only the users/sa/dba understand the causes.

ALTER PROCEDURE DBO.MYPROCEDURE
--
--
--
as
begin

begin
raiserror ('your message why its blocked to execute, any specific reason(s)',16,1)
return
END
--
--
--
END

Post #790754

Carleton

Posted Saturday, September 19, 2009 12:24 AM

SSC-Enthusiastic

Group: General Forum Members
Last Login: Friday, June 08, 2012 12:30 AM
Points: 150, Visits: 3,892

I like arun.sas' suggestion. If you need to keep the code in the sproc, you could just add what arun.sas suggested to the top of the procedure thereby 1) preventing it from being executed; 2) retaining the code in case in needs to be utilized; 3) provides a useful error message if it is attempted to be executed.

Cheers,
Carleton

Post #790756

cindy.hutchins

Posted Monday, September 21, 2009 7:35 AM

Grasshopper

Group: General Forum Members
Last Login: Monday, September 21, 2009 7:34 AM
Points: 17, Visits: 21

I ran the alter procedure and it worked very well for us. Thank you for all of your help.

Post #791111

« Prev Topic | Next Topic »

Permissions