Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Vivaldi
Constraint Violating Yak Guru
298 Posts |
 Posted - 2002-05-01 : 17:15:11
|
| SQL Spider men,I have been toying with the notion of full blown auditing of my applications. I attempt to write Internet Apps with DB backends. They are all in the records management systems area and each person logs in and some id is assigned to that person. When a person does an edit or delete, I want to log what happened. On older systems, they have a createdate,createid,changedate,changeid. I was hoping of setting it up so all record changes (besides the last one) could be logged. The only way I can think of doing this in a reusable format is through parsing the Sql Server logs, but this doesn't seem to simple, I know there are tools out there, but none appear to do what I need ( a non user interacton method for parsing logs).The other solution is to use triggers and a table.Any ideas, I couldn't find much for leads doing Google searches.Skol_________________________Death is one day closer |
|
|
VyasKN
SQL Server MVP & SQLTeam MVY
313 Posts |
Posted - 2002-05-01 : 18:47:20
|
| Use triggers or a product like Lumigent Log Explorer. Forget about parsing the log yourself, for there's no documentation on the tlog structure and is bound to change between versions. I wonder if Lumigent Log Explorer will work with Yukon, without a rewrite.--HTH,Vyashttp://vyaskn.tripod.com |
 |
|
|
|
|
|
|
|
Parsing Log Files