Re: triggers
From: Joe Celko (joe.celko_at_northface.edu)
Date: 02/16/04
- Next message: Anith Sen: "Re: Replace duplicates with blanks in outer join"
- Previous message: John Kane: "Re: Quering a Details table or Full-text indexing?"
- In reply to: ichor: "triggers"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 16 Feb 2004 11:43:22 -0800
>> is it ok to code triggers? do they have a very large performance
overhead like cursors do? <<
VERY GENERALLY SPEAKING, Triggers are not as bad as cursors because a
trigger does not leave the database, while a cursor can on either the
database or front end. A cursor in a front end program can be slowed
donw by the host program, too.
Avoid triggers when you can in favor of DRI actions. DRI can pass
implied predicates to the optimizer and a trigger cannot. The T-SQL
syntax does not port or conform to the ANSI/ISO model for triggers.
Think of triggers as by-pass surgery; you don't do it until you have
tried everything else.
--CELKO--
===========================
Please post DDL, so that people do not have to guess what the keys,
constraints, Declarative Referential Integrity, datatypes, etc. in your
schema are.
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
- Next message: Anith Sen: "Re: Replace duplicates with blanks in outer join"
- Previous message: John Kane: "Re: Quering a Details table or Full-text indexing?"
- In reply to: ichor: "triggers"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
