I will create a sql sox compliance audit for microsoft sql server

The Sarbanes-Oxley Act of 2002 is a law the U.S. Congress passed on July 30, 2002 to help protect investors from fraudulent financial reporting by corporations. AKA: SOX Act of 2002, it mandated strict reforms to existing securities regulations and imposed tough new penalties on lawbreakers.

It depends on what version of SQL you are running. Using TSQL for Azure SQL Auditing is not supported, hence using PowerShell. If your version of SQL Server is on-prem, it must be configured using TSQL. If you have both Azure and On-Prem, I'll help you configure both types of audits.

Usually the best way to setup audits is with a Server Level audit. But if your requirements require an Audit Action filter (if you need to reference a specific object like a table, stored proc or an entire database or schema) then you need a Database Level Audit. This is basically a custom config.

The general form for defining an action to be audited is: [action] ON [object] BY [principal] Examples: DATABASE::[dbname] and SCHEMA::[schemaname] INSERT, UPDATE on dbo.myTable by public SELECT on DATABASE::myDatabase by public DELETE on SCHEMA::mySchema by public

The T-SQL predicate (WHERE clause) used to filter audit logs. this is basically a filter to eliminate specific types of audit events.

Short Answer: “It depends” Long Answer: Yes, “IF” your SQL servers require the same level of auditing you can apply the same configuration on all of your servers.