This project is read-only.

Already have some existing column names

May 19, 2010 at 9:42 PM

I'm really impressed with the utility you have provided.  I'm at a bank, and this is exactly what we need.

However, the bank already had standards that we tried to follow, so we already have added four columns to almost every table: Created_By, Modified_By, Created_DateTime, and Modified_DateTime. We have not yet made the decision as to how they would be updated.  I'm working on the backend BizTalk tools, and we will have a front-end ASP.NET website updating the database.

I see our choices as:

1) strip out our columns, and use yours - which will automatically be handled by the trigger.

2) change your code to use our names instead of your names

Any advice or suggestions or other idea before I embark on the adventure.


Neal Walters



May 19, 2010 at 9:56 PM

I think it would be good if a future version of AutoAudit allowed you to configure those column names easily.

Aug 12, 2010 at 3:43 PM

I've added this to the wish list.

Nov 24, 2011 at 11:06 PM

Yep also in a similar position


currently the best option for us would be to modify the code to use our names.


Mar 8, 2013 at 5:43 PM
Looks like Version 2.00 includes a flag to not append these columns to the table selected for auditing.
Oct 31, 2013 at 6:02 PM
The latest release of AutoAudit 3.20e has a new feature that allows you to use any standard column name for the base table DDL column names

Those parameters are set starting at line 40 of the installation script.
Marked as answer by JohnSigouin on 10/31/2013 at 10:02 AM