Question: > 
> **Possible Duplicate:**  
> 
> [Are database triggers evil?](https://stackoverflow.com/questions/460316/are-database-triggers-evil) 
> 
> 
> 

There is lot of negative information on database triggers, just want to get the community's take on when is it good vs bad.

Answer: 
Database triggers are bad when they are used when other features are more appropriate.

Features which should be considered before attempting to use triggers:

Check constraints

Foreign key constraints

Unique indexes/constraints

(Persisted) computed columns

(Indexed) Views (if a trigger is attempting something like updating an aggregate, say)

Stored procedures (if direct table access can be prohibited)

After that point, triggers can be appropriately used without being "bad". Triggers should always be designed to have a small footprint.
Here are a few articles that should help you figure out by yourself for your needs.

1. [Pros and Cons of Triggers vs. Stored Procedures for Denormalization](https://stackoverflow.com/questions/2088905/pros-and-cons-of-triggers-vs-stored-procedures-for-denormalization) (SO question) ;
2. [Choice Between Stored Procedures, Functions, Views, Triggers, Inline SQL](http://www.paragoncorporation.com/ArticleDetail.aspx?ArticleID=28).

In short, `Triggers` are useful for the processing of massive amount of data, when complex DML has to be conducted. To answer your question, if this is not the case, you got your answer as per when a trigger is bad.