Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
I have not used a database trigger in years in the projects of the teams I have worked in, but I have seen them being used by other teams. Back in 2009, it seemed like a heated debate, but I am wo...
#2: Nominated for promotion
by
Alexei
·
2022-02-13T11:36:08Z (about 2 years ago)
#1: Initial revision
by
Alexei
·
2022-01-30T08:58:30Z (about 2 years ago)
In the current development context (2020+), is there any reason to use database triggers?
I have not used a database trigger in years in the projects of the teams I have worked in, but I have seen them being used by other teams. Back in 2009, it seemed like [a heated debate](https://stackoverflow.com/questions/460316/are-database-triggers-evil), but I am wondering if they are useful anymore for modern software applications. By modern software application I mean at least the following: - domain-centric as opposed to database-centric - way less business logic in the database - no direct database interaction - e.g. no linked servers or similar used to change data in the database from another application. Use APIs instead - code-first - database changes are almost always dealt with from the application code (e.g. migrations, data seeding) The only valid case where I created a trigger was to track DDL changes since some database objects were being changed without our team knowing it. However, this was not part of the normal development process.