Question for some of you sql pros out there. We have a web application that we are currently using to manage users for one of our sites. We are using a fairly standard table to log changes to users records like I've seen used over and over again though the
years...
Example schema:
CREATE TABLE [dbo].[ChangeTracker](
[DateOfChange] [datetime] NOT NULL,
[UserId] [int] NOT NULL,
[ChangeId] [int] IDENTITY(1,1) NOT NULL,
[Category] [varchar](25) NOT NULL,
[Action] [varchar](100) NULL,
[AffectedId] [int] NULL,
[TableName] [varchar](50) NULL,
[FieldName] [varchar](50) NULL,
[ValueOrg] [varchar](255) NULL,
[ValueNew] [varchar](255) NULL
I'm sure you have all seen something similar. I just started researching SQL Server Audit. I have not come close to reading everything I should yet, but can anyone comment as to wether or not we might be able to replace the simple ability to show changes
using this table by replacing it with the SQL Audit?
It sounds like overkill to me but that is the question I have been posed with.
Thanks in advance, Hal