SQL Server Performance

SQL:Stmt Completed v SQL:Batch Completed

Discussion in 'SQL Server 2005 Performance Tuning for DBAs' started by Jack Vamvas, Apr 29, 2008.

  1. Jack Vamvas Member

    Hi
    I'm troubleshooting a performance issue , Looking at Profiler - for the given statement, I'm getting the following figures , why would there be such a disparity between the figures. ? How can I go about finding out why there is such difference?
    SQL:Stmt Completed:CPU = 31, Reads = 129 , Duration = 32
    SQL:Batch Completed: CPU = 2531, Reads = 6087 , Duration = 2593
    Jack
  2. preethi Member

    Hi Jack,
    SQL: Batch completed is for the entire batch. It may contain many statements. (or the same statement is executed multiple times) Where SQL:stmt Completed is for a single statement.
    Unless your batch contains only a single statement, there is nothing amzing about this.
    However, the batch cost is soemthing I consider as serious, if it is not part of a "once in a way" transaction. Can you produce the statements on the batch please.
  3. Jack Vamvas Member

    The statement I'm running from Query Analyzer is :
    SELECT myCo1,myCol2 FROM myTable
    INNER JOIN MyTable2 ON myTable.thecol = myTable2.thecol



    SQL:Stmt Completed:CPU = 31, Reads = 129 , Duration = 32
    SQL:Batch Completed: CPU = 2531, Reads = 6087 , Duration = 2593

    Do I need to save out any other events?

Share This Page