What if there is another application (or e.g. a stored procedure) that uses this DB table so you cannot control all saving operations from your application?
Don't do that. A DB table is too big and complex a surface to use as an interface between multiple applications. Each table should have one clear owner; if multiple components need to access the same table, put it behind a service rather than having them access it directly.
