|
-
November 16th, 2005, 03:17 AM
#1
 Advice on DB Design of 'Audit' Trail
If one wants to log all the fields that has been edited (Original to Modification, Date of Edit, etc...) how should one design it?
Database is Access and SQL Server...
Intelligent people talks because they have something to say,
Fools talk because they have to say something....
-
November 16th, 2005, 09:22 AM
#2
Re: Advice on DB Design of 'Audit' Trail
It depends on what all events are you trying to follow up and what all information regarding those modifications are you planning to keep into the DB. You could set trigger to the tables whose data modifications you want to track... so that whenever there is a successful INSERT, UPDATE or DELETE called on those tables the information is stored in a seperate table for you. You would need to exploit the fact that there are two tables that you get access to in the triggers - "inserted" and "deleted". Hope this helps. Regards.
Can you help me with my homework assignment?, Before you post!, Use code tags, How to post!, Codeguru technical FAQs, C++ FAQ Lite, Stroustrup: C++ Style and Technique FAQ, Guru of the Week, Comeau C and C++ FAQs, Comeau C++ Templates FAQs, CUJ @ DDJ, Spam threshold
 My Blogs : Learning C++ is fun | Abnegator's reflections
Open Threads : C++ Aha! Moments | Nature of work in C++?
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|
Reply With Quote
