My SP looks like this that originally populates the record set.
CREATE PROCEDURE dbo.sp_insert_file
@.KBID int,
@.rev int,
@.filename nvarchar(50),
@.moddate datetime,
@.owner nvarchar(50),
@.author nvarchar(50)
As
INSERT INTO KBFile
(KBID, rev, filename, moddate, owner, author)
VALUES (@.KBID,@.rev,@.filename,@.moddate,@.owner, @.author)
GO
I need to have a stored procedure that will select a recordset based on KBID(PK) and archive the entire record set to another table. I then need to be able to UPDATE the individual records for this record set in the KBFile table.
I am trying to create an 'audit' trail while maintaining previous records.
Can someone point me in the right direction?
What about using an update trigger ? You will be able to audit all change events (not only these from stored procedures)HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de|||
Often, a TRIGGER is used for Audit trails since the TRIGGER execution cannot be avoided. Audit trails are more 'risky' when stored procedures are used.
You might find one of these references pointing to the use of TRIGGERS to be helpful:
Trigger -Audit Trail
http://www.nigelrivett.net/AuditTrailTrigger.html
http://www.sqlservercentral.com/columnists/sjones/auditingyoursqlserverpart1.asp
http://www.sqlservercentral.com/columnists/sjones/auditingyoursqlserverpart2.asp
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_create2_7eeq.asp
No comments:
Post a Comment