• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 543
  • Last Modified:

Can I read the transaction log?

I want to know what changes makes a program to a database.
I don't know what tables may be affected, or if it's updating, deleting or inserting records in one or more tables.
So I can do 2 things:
Compare the whole database "before" and "now"
Read the transactions that where inserted in the transaction log

I think the second solution might be easier, because the database is quite big...

So, how can I do it (step by step)?
0
Chofo
Asked:
Chofo
  • 5
  • 5
1 Solution
 
arbertCommented:
Nope, you really can't read the transaction log in a meaningful manner.  HOWEVER, there are a couple of third party products that will read the log for you.  LogExplorer http://www.lumigent.com   and NetIQ also has a product http://www.netiq.com.

If you really need to capture "audit track" type information, you'll almost have to add triggers to the table and insert the before and after changes into another table.

Brett
0
 
ChofoAuthor Commented:
Brett: thank you for your answer, it's good to know which are all the different approaches to the subject

I've just downloaded a free trial, and I'm also developing some triggers to find out which tables change...
but I don't know how to learn what changed in the table without having to compare the whole table "before" and "after".
For instance, if the "delete" triggers, how do I know which record was deleted?
Is there a shortcut?
0
 
arbertCommented:
Basically, if you have good primary keys on your table, you will know what record was updated, deleted, or inserted.


Here are a couple of useful links on auditing:

http://www.sql-server-performance.com/auto_audit_2_spotlight.asp
http://www.nigelrivett.net/AuditTrailTrigger.html


Brett
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
ChofoAuthor Commented:
Brett:
I don't quite agree with your statement about primary keys, updates will tend to be next to the bottom, but that's not necessary...

Thanks for the links...

Chofo
0
 
arbertCommented:
"next to the bottom"  what do you mean?  If the table has a primary key on it, you know EXACTLY what record was affected by an operation..........
0
 
ChofoAuthor Commented:
But... how do you know the ID of the record updated?
I can get if it was an update, delete or insert;  but how do I know the ID of the primary key?
0
 
arbertCommented:
What do you mean the "ID of the primary key"?  If you know the primary key, that is the exact key that is needed to find a record in the database.....
0
 
ChofoAuthor Commented:
OK, ID, primary key, it's the same to me.   How do you know which was the record affected by the table update, delete or insert?   Is it there an SQL variable containing the primary key of the last record updated, deleted or inserted?  What's its name?   How do I get the value?
Or else, can I get the "SQL string" executed over the table?
0
 
arbertCommented:
Nope, you have to know the primary key.  If you're coding the trigger or stored proc, I would hope that you know what it is.

As far as getting the SQL string that executed, the only way to do that (right now anyway) is with profiler.  When you try and get the sql from within a trigger (fn_get_sql) it returns the actual code of the trigger (thanks microsoft)....
0
 
ChofoAuthor Commented:
OK, thank you very much!
You've been really helpful...

Chofo
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

  • 5
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now