Re: xp_cmdshell access

From: Dan Guzman (danguzman_at_nospam-earthlink.net)
Date: 04/07/04

  • Next message: Hari: "Re: Bulk Insert" 
    Date: Tue, 6 Apr 2004 19:47:58 -0500

    Are you executing xp_cmdshell from a dbo-owned stored procedure? In this
    case, you can turn on the cross-database ownership chaining option
    (introduced in SP3) in your user database so that direct xp_cmdshell execute
    permissions are not required. For example:

        EXEC sp_dboption 'MyDatabase'. 'db chaining', true
        GO

    Note that you should turn on cross-database chaining in an sa-owned database
    only if you fully trust users with permissions to create dbo-owned objects. 

    -- 
Hope this helps.
Dan Guzman
SQL Server MVP
"VC" <anonymous@discussions.microsoft.com> wrote in message
news:DF5DFEFB-E047-4189-B774-A3B7F1926CB1@microsoft.com...
> I am having the same problem. My proxy account worked fine until the SP3a
install. Before SP3a, I did not have to set public permissions to
xp_cmdshell.
> My DB is owned by 'sa'.
> I am unsure how to fix it. Any suggestions would be great.
  • Next message: Hari: "Re: Bulk Insert"