Scans

  • Hi,

        I'm trying to use profiler to identify scans, however I'm not able to match the profiler results to the excution plan.

    Below is the excution plan

    Execution Tree

    --------------

    Sort(ORDER BY[pax_schema_rules].[label_type] ASC, [pax_schema_rules].[rule_type] ASC, [pax_schema_rules].[rule_line] ASC))

      |--Clustered Index Seek(OBJECT[Pax-DBA].[dbo].[pax_schema_rules].[PK_pax_schema_rules]), SEEK[pax_schema_rules].[page_id]=[@PageID] AND [pax_schema_rules].[schema_item]=[@Item]) ORDERED FORWARD)

    Now according to profiler this sproc contains 1 scan

    Now I know I'm missing something somewhere, but I thought I'd beable to locate the SCAN in the excution plan

    I'm no expert but this plan does not contain any scans, can anyone help?

    TIA

     

     

  • Hi,

    If you want to know whether the query is using a seek or a scan.

    click on the query execution plan which will be on the  right side top

    of the

  • Hema, I think what Rafter posted is the Execution plan.

    Rafter, simple question, are you sure you have the right plan for the right SPID?

     

     

    --------------------
    Colt 45 - the original point and click interface

  • Yes, its definately the same SPID, the table has a clustered index and according to the excution plan (posted above) is being used with an index seek, but profiler indicates a scan

    Do clustered index seeks appear as scans?

    Thanks

    Matt

  • Maybe the scan is being produced by another T-SQL statement.

    Best way to isolate this is to run the statement in Query Analyzer with "Show Execution Plan" turned on.

     

    --------------------
    Colt 45 - the original point and click interface

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply