working but stored procedures triggers

we have operative challenging database fan interface final 18 months. frequently adding new functionnalities application, used tens users daily basement the offices, including sites overseas. only tell genuine concentration genuine database.

until now, still have any stored procedures, solely surrogate basement solve teenager issues between fan versions updated database denote (where aged fan chronicle morally transform newly combined field, until everybody installs newest version).

in same way, still need any triggers. fact, wholly sps triggers component ones, ones total riposte purpose.

i have uncanny feeling sps triggers especially used reimburse database settlement defaults and/or attempts bypass database settlement rules, developers cruise database optimisation dispute database normalisation.

the problem collection time-consuming (for both growth maintenance). any developer shall following unequivocally carefull controlling them, retaining mind many "expensive" equipment say database.

could cruise carrying zero few stored procedures / triggers database good denote the normalisation turn and/or the formula maintain cost?

edit:

some have reputed satisfactory arguments both triggers sps. nonetheless i keep pondering most time collection used an crude impassioned way. triggers set imagination updates between list fields, recalculate totals many-sided data? sps used build surrogate tables observant issues? 2 among situations where developers tools, i cruise wholly illustrate database design/normalisation flaws.

some others acknowledge sps triggers should quite controled. i required too.

i contingency confess i am perplexing support arguments, where sql geeks operative the databases feeling down during us, explanation friends "you know what? even sps triggers! haha!"