PRB: ObjectID Filter in SQL Profiler Triggers Only with Specific Events

Article translations Article translations
Article ID: 303445 - View products that this article applies to.
This article was previously published under Q303445
Expand all | Collapse all

SYMPTOMS

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.

CAUSE

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.

WORKAROUND

Filter by object name instead.

Properties

Article ID: 303445 - Last Review: October 17, 2003 - Revision: 3.2
APPLIES TO
  • Microsoft SQL Server 2000 Standard Edition
  • Microsoft SQL Server 7.0 Standard Edition
Keywords: 
kbpending kbprb KB303445

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com