3 ms·
Thanks for your thoughtful comment on this. It’s interesting to hear good use cases for triggers. Some years back I worked at a place that went deep on trigger
by aidos 8y ago
Thanks for your thoughtful comment on this. It’s interesting to hear good use cases for triggers.
Some years back I worked at a place that went deep on triggers and stored procedures and it totally put me off using either (sql server). There was a lot of opaque behaviour that was hard to debug and performance was terrible.
A friend is a great dB developer (one of the top on stack exchange) and when I asked him about triggers he said that he doesn’t use them for updating data, ever, unless it’s someone else’s totally broken schema and he has to dig himself out of a hole.
On the other hand, he loves stores procs and pretty much every interaction he lets apps have with the dB run through stored procs. What are your thoughts on how heavily you should lean on stored procs?