Having the full history isn't as important as being able to see what was just changed, but obviously I can give them the option of both which is at the...

Sean Lange (9/6/2011)

---

david.holley (9/6/2011)

---

Sean Lange (9/6/2011)

---

These are the exact challenges I was suggesting you would run into in your original thread about these auditing triggers. It is challenging to put...

Roy Ernest (9/6/2011)

---

There are lots of articles on Change tracking and Change data control. You would be able to chose what technology you want to use based on the business...

Sean Lange (9/6/2011)

---

These are the exact challenges I was suggesting you would run into in your original thread about these auditing triggers. It is challenging to put these records back...

Roy Ernest (9/6/2011)

---

Just out of curiosity, since you using SQL Server 2008, why did you not look for the tools provided be them? CT, CDC and SQL Audit? They have...

The example that I posted is only the section that handles the Deletes, another section will handle Inserts with another handling Edits. The trigger is designed to work AFTER INSERT,...

It'll be more along the lines of this...

INSERT INTO

ProjectInformationChangeLog

(Action, Element, WindowsUserId, DateTimeStamp, SQLServerTable, ShowNumber)

SELECT ShowNumber,'Delete', 'General Information', SYSTEM_USER, SYSDATETIME(), OBJECT_NAME(@@PROCID) From deleted GROUP BY ShowNumber WHERE ProjectNumber In (Select...

Sean Lange (9/1/2011)

---

david.holley (9/1/2011)

---

Since the 'inserted' and 'deleted' record sets include all records touched by an INSERT, UPDATE or DELETE, I'm assuming that could determine which actions where performed on...

In the original conceptualization, I was going to use the sp to create a record in the ChangeLog and then capture the values of the record before & after the...

Your Name Here (8/26/2011)

---

FWIW, I've tried both approaches (sp-controlled audit vs. triggers) and found that the trigger approach had the least amount of care and feeding in the long run....

Sean Lange (8/25/2011)

---

I think varchar would be fine with one possible exception. DateTime. If you are only going to use this for reporting it might be ok as a varchar...

Since the data is essential dead end and won't have any relationships to external tables, would you recommend going with varchar for the datatypes? Unicode characters won't be applicable. The...

Sean Lange (8/25/2011)

---

The one thing you seriously need to consider is how you are going to pull data to give a snapshot view at a point in time. Take a...

Thanks yall for the input here the general direction that I'm going. There are still some things to hammer and fine tune such as denormalizing the _Audit tables. (The fact...

It just occurred to me that I'll have to use the stored proc to capture the before and after records and not use triggers at all. Since I have a...