Hi Pola,
With further researching, no-gui, no-interactive/unattached and no
output/echo application is OK for xp_cmdshell.
As xp_cmdshell is run under the SQL Server Service with its startup
account, something will be lost in the security context of permissions
passed to the application outside of SQL Server layers. If your application
is associated with this security context, it will not work fine without the
proper permission(s). Even though we can start SQL Server Service from a
command prompt with the ¨Cc parameter to bypass this security context,
that might not be your expected startup behavior (not start as a Windows
Service) on SQL Server.
Using Startup Options:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad
_1_start_8m43.asp
I think that¡¯s one of the reasons that Aaron suggested running the
executable file out of the SQL Server layer. In addition, application
outside of SQL Server can check the trigger inside SQL Server and execute
another executable file gracefully, which can be another way.
Thanks very much.
Best regards,
Yanhong Huang
Microsoft Community Support
Get Secure! ¨C
www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.