Trigger performance overhead
281875Jul 29 2003 — edited Jul 30 2003Does anyone know there is a performance overhead if using trigger to check the data integerity?
The case is we want to check whether the master record has been used in child tables, if yes, don't not allow to update the master record as "disabled".
Is it better to check this in before-update trigger or check in application??