Posted by John Bell on 09/17/05 20:30

Hi

You are looking at the client statistic! The topic "Query Window Statistics
Pane" in books online explains their values.

Time is a good indicator of performance, for instance if there are more
network round trips this should be noticed in the time taken. You may also
want to consider the number of reads/writes which may give some indication
of how well it will perform when the system in under a load. These can be
viewed using SQL profiler.

Expect the first time you run a query to take longer than subsequent times,
if your query is cached subsequent executions may be significantly faster.
Use DBCC FREEPROCCACHE and DBCC DROPCLEANBUFFERS to clear the procedure
cache and buffer pool.

John



"laurenq uantrell" <laurenquantrell@hotmail.com> wrote in message
news:1126976566.998344.13050@g44g2000cwa.googlegroups.com...
>I am trying to determine which of three stored procedure designs are
> fastest in the Query Analyzer:
>
> One query is a straight SELECT query with all desired rows and a dozen
> (tblName.RowName = @param or @param = Null) filters in the WHERE
> statement.
>
> One query populates a #Temp table with the UniqueIDs from the results
> of the SELECT query in the above example, then joins that #Temp table
> to get the desired rows.
>
> One query users EXEC sp_executesql @sql, @paramlist, @param
> in which the @param has the dozen filters.
>
> What I'm trying to determine is which is the fastest.
>
> Each time I run the query in Query Analyzer it returns the same
> recordset (duh!) but with much different Time Statistics.
>
> Are the Time Statisticts THE HOLY QRAIL as far as determining which is
> fastest, and what so I want to look at, the Vale or the Average? I
> notice there are different numbers of bytse sen and bytes received for
> each of the three queries.
>
> Any illumination on this is appreciated.
> lq
>

[Back to original message]