Re: Application role to access xp_cmdshell

From: Carl Olsson (caos_at_regerar.com)
Date: 02/18/04 

Date: 17 Feb 2004 23:16:30 -0800

Thanks Dan for your excellent explanation. But unfortunately I'm still
at SQL 7... Any other options?

Carl

"Dan Guzman" <danguzman@nospam-earthlink.net> wrote in message news:<#kQj98V9DHA.3176@TK2MSFTNGP11.phx.gbl>...
> As long as the ownership chain is unbroken, direct permissions on
> xp_cmdshell are not needed. This necessitates that your user procs be owned
> by 'dbo', your user database be owned by 'sa' and cross-database chaining
> (intoduced in SQL 2000 SP3) be enabled. Example script below.
>

Relevant Pages

  • Re: Stored Procedure Security Problem
    ... To add on to Russell's response about the ownership chain, permissions on the underlying objects are not needed as long as the ownership chain is unbroken. ... The ownership chain is considered unbroken as long as all objects involved have the same owner but, as Russell mentioned, dynamic SQL always breaks the ownership chain and direct permissions are then required. ... one needed to only examine the schema name to determine ownership since schema and owner were the same thing. ...
    (microsoft.public.sqlserver.security)
  • Re: Formatting issue
    ... The SQL is so long-winded that I'm bumfuzzled ... Here's my SQL for the query: ... "John Spencer" wrote: ... Carl Rapson ...
    (microsoft.public.access.queries)
  • Re: Why do IT guys hate MS Access?
    ... > require you give the user full authority on the Tables in the SQL ... > Server host. ... In the ADP/MSSQL apps I've developed I give no direct permissions to the ...
    (comp.databases.ms-access)