Home/ Questions/Q 7989643
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-04T12:48:42+00:00

I’m using triggers to audit table changes. Right now I capture the individual column

  • 0

I’m using triggers to audit table changes. Right now I capture the individual column changes in the following:

DECLARE @statement VARCHAR(MAX)
SELECT @statement =
'Col1: ' + CAST(ISNULL(Col1, '') AS VARCHAR) + ', Col2: ' + CAST(ISNULL(Col2, '') AS VARCHAR) + ', Col3: ' + CAST(ISNULL(Col3, '') AS VARCHAR)
FROM INSERTED;

The problem is, I need to tweak the column names for every table/trigger that I want to audit against. Is there a way I can build @statement, independent of the table using a more generic approach?

cheers
David

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    what you need to do is build a memory table using the following query and then loop through the same to produce the SQL statement you want

    select column_name from information_schema.columns
    where table_name like ‘tName’
    order by ordinal_position

    however i am not sure this would be the right thing to do for AUDIT. How are you going to pull it back later. Say in one of your releases you happen to drop the column what will happen then? how will you know which column held which data.

    • 0