Yes you are right. I missed that part.
I am doing multiples deletes at a time using the front end of the application that is through ADO.Net recordset.
Do you think any other alternate solution to do this?
Sorry, lost track of the thread in the shuffle yesterday.
So, you are getting multiple delete statements sent down. There's no way to handle this, then, via trigger. The trigger has no idea what you're trying to attempt and its mechanics don't behave that way. The only workaround I could think of is setting the audit parameter manually from ADO and forcing it to send the same time on its 'batch'.
Even that's not really a good solution. What you really want it to do is have the ADO call a proc that does a mass delete and let the timestamp and trigger behave properly. All the items will end up with the same timestamp since they enter the trigger simultaneously in the deleted table.
- Craig Farrell
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake. For better assistance in answering your questions | Forum Netiquette
For index/tuning help, follow these directions. |Tally TablesTwitter: @AnyWayDBA