Re: trigger each row

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Tibor Karaszi (tibor_please.no.email_karaszi_at_hotmail.nomail.com)
Date: 10/07/04 

Date: Thu, 7 Oct 2004 14:14:56 +0200

I understand what you are saying. But seen from another perspective:

"I'm glad that SQL Server doesn't support row-level triggers. Thanks to this a lot of code runs
significantly faster as it has made people realizing the logic set-based instead of procedural."

I understand that it doesn't help you in a case where you can't redo the logic in the procedure to
make it set-based. 

-- 
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Thomas Steinmaurer" <t.steinmaurer@_no_upscene_spam_.com> wrote in message 
news:%23nLEOZGrEHA.2008@TK2MSFTNGP12.phx.gbl...
>> If  you *have* to call an SP for every row then you can only use a cursor
> /
>> WHILE loop approach. This is a poor solution. You should avoid using
>> row-by-row processing in a trigger. Why can't you put the logic from your
> SP
>> into the trigger instead?
>
> It's a pitty that MSSQL doesn't support row-level triggers at all. It
> would make life in certain situations more easier.
>
>
> Best Regards,
> Thomas Steinmaurer
> LogManager Series - Logging/Auditing Suites supporting
> InterBase, Firebird, Advantage Database and MS SQL Server
> Upscene Productions
> http://www.upscene.com
>
>
>
>