This article was previously published under Q303445
This article has been archived. It is offered "as is" and will no longer be updated.
In SQL Server Profiler, you can use the ObjectID filter to trace activity in specific objects. However, the filter does not work with all events. Examples of events that do use the ObjectID filter are Locks and Scans. T-SQL Events cannot make use of the filter.
ObjectID filters trigger as long as the ObjectID is known when tracing occurs. For instance, enable the "Lock:Acquire" and "Statement Starting" events with the ObjectID filter. The Lock:Acquire event is filtered out correctly because the server is already aware of the ObjectID of the given table. However, the ObjectID filter for "Statement Starting" does not work because its ID is not set in trace data yet.