Tuning Indexes - Professional SQL Server 2005 Performance Tuning - page 376

SQL Server Execution Times:
CPU time = 0 ms, elapsed time = 1 ms.
SQL Server Execution Times:
CPU time = 0 ms, elapsed time = 1 ms.
SQL Server Execution Times:
CPU time = 922 ms, elapsed time = 10464 ms.
This shows that the cold run took almost 10 seconds to complete.
The warm run looks like this:
SQL Server parse and compile time:
CPU time = 0 ms, elapsed time = 1 ms.
SQL Server parse and compile time:
CPU time = 0 ms, elapsed time = 1 ms.
Table '#boys'.
Scan count 0, logical reads 1003, physical reads 0, read-ahead reads 0, lob logi-
cal reads 0, lob physical reads 0, lob read-ahead reads 0.
Table 'people'.
Scan count 1, logical reads 1895, physical reads 0, read-ahead reads 0, lob logi-
cal reads 0, lob physical reads 0, lob read-ahead reads 0.
SQL Server Execution Times:
CPU time = 47 ms, elapsed time = 216 ms.
(1000 row(s) affected)
Table '#girls'.
Scan count 0, logical reads 1003, physical reads 0, read-ahead reads 0, lob logi-
cal reads 0, lob physical reads 0, lob read-ahead reads 0.
Table 'people'.
Scan count 1, logical reads 1765, physical reads 0, read-ahead reads 0, lob logi-
cal reads 0, lob physical reads 0, lob read-ahead reads 0.
SQL Server Execution Times:
CPU time = 47 ms, elapsed time = 46 ms.
(1000 row(s) affected)
SQL Server Execution Times:
CPU time = 0 ms, elapsed time = 1 ms.
Table '#boys'.
Scan count 1, logical reads 4, physical reads 0, read-ahead reads 0, lob logi-
cal reads 0, lob physical reads 0, lob read-ahead reads 0.
SQL Server Execution Times:
CPU time = 0 ms, elapsed time = 3 ms.
Table '#girls'.
Scan count 1, logical reads 4, physical reads 0, read-ahead reads 0, lob logi-
cal reads 0, lob physical reads 0, lob read-ahead reads 0.