Post reply

XP_cmdshell inside Trigger

  • August 9, 2008 at 11:41 am

    #855703

    As I mentioned before, the login used by the application is irrelevant. Anything run by xp_cmd shell is run under the security credentials of the SQL Server Service account, not that of the user that is running the application.

    You need to find what account SQL Server is running as (try the configuration manager) and see whether that account has enough rights to run the cache clearing tool. Then set the app so that it's not using sa.

    Are you doing your inserts/updates/deletes via a stored procedure? If so, do the cache clear from the proc. That kind of thing doesn't really belong in a trigger. A second is a long time for a single row insert/update/delete transaction to remain open

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

Viewing post 16 (of 15 total)

You must be logged in to reply to this topic. Login to reply