Microsoft KB Archive/303445

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

Article ID: 303445

Article Last Modified on 10/17/2003

-

APPLIES TO


 * Microsoft SQL Server 2000 Standard Edition
 * Microsoft SQL Server 7.0 Standard Edition

-



This article was previously published under Q303445



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 &quot;Lock:Acquire&quot; and &quot;Statement Starting&quot; 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 &quot;Statement Starting&quot; does not work because its ID is not set in trace data yet.



WORKAROUND
Filter by object name instead.

Keywords: kbprb kbpending KB303445

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.