Technically log replication has everything done by everything, and if you are careful with triggers you can also track everything as well, using a DDL/DML captu

Technically log replication has everything done by everything, and if you are careful with triggers you can also track everything as well, using a DDL/DML capture table(DCL too if you're worried!). These approaches work on basically every type of SQL solution that uses WAL/triggers. For your specific question I have a trigger approach many times in SQL Server but it has a tendency to slow things down if you are logging every query so designing an insertion mechanism that doesn't bog down production isn't perfect, and you might want to perform some sampling.