you should start a new thread to get the best help, since this thread is four years old or so. also, the forum is related to Access, but you really mean SQL, right?

so are you sure you want to paint yourself in a corner with a rule that says absolutely, positively, without a trigger AND you need whodunnit information?

a trigger is the best way to handle that requirement, i would say.

For data changes, you can use SQL Temporal Tables, Change Data Capture to track what specific data changed, Change Tracking to capture which data changed, but neither has who did it information.

For whodunnit changes, SQL Audit or an Extended event has who changed the data, but not the details of which specific data was changed.

I'm under the impression that the only place for both data and user info is at the trigger level, unless someone can correct me on my conceptions/misconceptions.