RE: SQL Profiler: Attention Event class on DELETE statement - why?
- From: v-mingqc@xxxxxxxxxxxxxxxxxxxx (Michael Cheng [MSFT])
- Date: Tue, 08 Nov 2005 10:56:33 GMT
Hi Jeff,
>> What our DB Admins would like to know is why is the return code coming
back
>> as SQL_SUCCESS, when all the triggers haven't even completed.
Since your SQLExecDirect is executing DELETE statement, when DELETE was
done, SQL_SUCCESS will be returned. Trigger was only launched internal SQL
Server and you cannot decide whether trigger was done or not.
I recheck the original post. For your scenario(using trigger to do the
update), you will have to redesign the business logic to avoid the update's
roll back.
For example, create a stored procedure, let the stored procedure to the
DELETE, AUDIT and UPDATE in a transcation. Let you program call the stored
procedure
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
.
- References:
- RE: SQL Profiler: Attention Event class on DELETE statement - why?
- From: Michael Cheng [MSFT]
- RE: SQL Profiler: Attention Event class on DELETE statement - why?
- Prev by Date: RE: SQL Profiler: Attention Event class on DELETE statement - why?
- Next by Date: Re: Locks per File
- Previous by thread: RE: SQL Profiler: Attention Event class on DELETE statement - why?
- Next by thread: RE: SQL Profiler: Attention Event class on DELETE statement - why?
- Index(es):
Relevant Pages
|
Loading