A while ago we dropped some xp_real-functions in a production database,
because of some security issues. Executing the following create statement as DBA: create function dbo.xp_real_cmdshell( in command varchar(8000) default null, in redir_output char(254) default '' ) returns integer internal name 'xp_real_cmdshell' go results in an error message: Could not execute statement. Does anybody know how to solve this problem? |
There isn't a way to do this on an existing database that I know of - the server will not permit anyone (including a DBA) to link a new procedure to an internal server mechanism. To get the system procedures back, dbinit a new database, and do an unload/reload into it. ...and that's why the "secure server features" have been introduced with v10, right?
(01 Dec '11, 07:30)
Volker Barth
I was hoping to avoid creating a new database. Was hoping on something like
(01 Dec '11, 07:47)
Dan Jernberg
|