Post reply

Permissions for DML trigger?

  • August 7, 2008 at 9:50 am

    #130621

    Hey all,

    Minus giving the user db_owner, what privileges can I grant to allow a DML (update) trigger to run when updating a table? The user currently has read/write/execute and I receive the following when attempting to update the table with the specified account?

    Msg 59003, Level 16, State 1, Procedure z$TASKS_TU, Line 93

    Attempt to Update Table "TASKS" failed for DEPT = "Client Communications" with access level = "0"

    Msg 3609, Level 16, State 1, Procedure jmp_UpdateNote, Line 33

    The transaction ended in the trigger. The batch has been aborted.

    Thanks!

  • August 7, 2008 at 9:56 am

    #854564

    It shouldn't need any extra permissions, and that is not a standard error message. It's custom and specified within the trigger (message number of > 50000)

    What's the code of the trigger?

    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

  • August 7, 2008 at 10:18 am

    #854581

    Good call Gila ... I didn't even notice that. Don't use triggers much ... but after digging through the trigger and finding out what they were doing, I was able to resolve it. Stupid third party vendor applications.

    Thanks

  • August 7, 2008 at 10:31 am

    #854589

    Adam Bean (8/7/2008)

    Stupid third party vendor applications.

    Lol.

    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 4 posts - 1 through 3 (of 3 total)

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