SQL Profiler, How setup trace to monitor one table.

[cburns70]

We're having problem were one column in a table is being updated when it's not supposed to. We're trying to nail down why this is happening.

I would like to setup a trace on this table, but I'm having some trouble.

When I setup the trace; I'm saving the trace to a table (tracetable), I set my filters for database id and object id.

But when I run the trace I get thousands of rows of info (in a matter of minutes) showing the inserts for the tracetable.

How can I set the trace to only report on the table I want to monitor? Ideally I would like capture when, who and what modified the column.

I want to run this trace continuously since the problem is very random, sometimes occurring weeks apart. Since it may run for a long period I don't want to capture any other info. This table does not get updated frequently either.

Any help would be appreciated.

 

[JayKusch]

Why not create a trigger on the table and capture the needed info?

Thanks

J. Kusch

 

[JayKusch]

Here is a link with an example of how a trigger would work for you.

Now if it is a heavily trafficed table, you may want to test out performance.

http://www.simple-talk.com/sql/data...s-sql-server-faq-no.5-pop-on-the-audit-trail/

Thanks

J. Kusch