![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
|
Thank you for your response. I investigated Scan:Started and Scan:Stopped events, as well, but they are fired even for index seeks. I'd like to identify them and exclude them from my trace. There is a "Mode" column that I can filter on: 1 = Normal 2 = First 4 = Back 8 = Unordered 16 = No data 32 = Reserved 64 = Exlatch 128 = Index supplied 256 = Marker but what is the meaning of those? How do I distinguish scans only? On Jul 3, 12:30 pm, "Uri Dimant" <u... (AT) iscar (DOT) co.il> wrote: vlerhttp://www.sql-server-performance.com/tips/sql_server_profiler_tips_p.... "vler" <VladaE... (AT) gmail (DOT) com> wrote in message news:928fe53c-59ac-41b7-afbf-b825bea94935 (AT) 34g2000hsh (DOT) googlegroups.com... Hi, I'm using SQL Server 2000 sp4. Huge database (100+ tables), huge application. Is there a way to use SQL Profiler to filter out all table/index scans? I get some info with SP:Completed and SP:StmtCompleted ("Reads" column) but especially for cascade deletes I cannot easily figure out what's being scanned. Runing the query in QueryAnalyzer gives me the info, but I'd need to identify the queries first. Thanks!- Hide quoted text - - Show quoted text - |
![]() |
| Thread Tools | |
| Display Modes | |
| |