query statistics

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 7,2000 » Performance Tuning » query statistics

query statistics

Rate Topic

Display Mode

Topic Options

Author

Message

niranjankumark

Posted Saturday, October 13, 2007 4:32 AM

Forum Newbie

Group: General Forum Members
Last Login: Saturday, October 13, 2007 5:59 AM
Points: 3, Visits: 3

My query is running very slow , i used index, defragmentation, querytuning . but still performance not improved. this report is statistics report, based on this what to improve in my query.I wish to know what are all things has to be improved based on this report.

COUNTER Value Average

Application Profile Statistics

Timer resolution (milliseconds) 0 0

Number of INSERT, UPDATE, DELETE statements 0 0

Rows effected by INSERT, UPDATE, DELETE statements 0 0

Number of SELECT statements 2 2

Rows effected by SELECT statements 1.70022e+006 1.70022e+006

Number of user transactions 7 7

Average fetch time 0 0

Cumulative fetch time 0 0

Number of fetches 0 0

Number of open statement handles 0 0

Max number of opened statement handles 0 0

Cumulative number of statement handles 0 0

Network Statistics

Number of server roundtrips 3 3

Number of TDS packets sent 3 3

Number of TDS packets received 28569 28569

Number of bytes sent 2054 2054

Number of bytes received 1.16501e+008 1.16501e+008

Time Statistics

Cumulative client processing time 974 974

Cumulative wait time on server replies 2.28888e+009 2.28888e+009

Post #410278

Jeff Moden

Posted Saturday, October 13, 2007 10:20 AM

SSC-Dedicated

Group: General Forum Members
Last Login: Yesterday @ 9:57 PM
Points: 32,893, Visits: 26,771

This is very nearly a duplicate post...

http://www.sqlservercentral.com/Forums/Topic410280-65-1.aspx

The only thing that means anything about performance for all the timers you have here is this...

Number of TDS packets received 28569 28569
Number of bytes sent 2054 2054
Number of bytes received 1.16501e+008 1.16501e+008

It means you asked for a lot of data... and got it... The number of bytes returned are in excess of 100 million bytes and you did it all with two selects. That's a lot of information to stream over a pipe...

--Jeff Moden

"RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".

First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column."

For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

Post #410345

« Prev Topic | Next Topic »

Permissions