Your answer is one click away!
Is it advisable to use Triggers in SQL Server to implement Audit trail on very frequently updated tables which contains large data? Are there any performance impacts? If not recommended, what are the options for implementing Audit trail?
You might want to investigate Change Data Capture. It is native sql server functionality for audit logging.
CDC does add overhead, but it is well though-out overhead. Triggers can get messy very quickly and should be avoided when possible.