Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-users: [Wireshark-users] (no subject)

From: "Gaudineer, Kevin" <GAUDINKL@xxxxxxx>
Date: Wed, 8 Jul 2009 10:29:49 -0500

Hello Wireshark users,

 

Does anyone have experience with TDS (Tabular Data Stream) analysis with WireShark?  I am working with a vendor who is insistent that there is a network problem with an application that is using TDS and I don’t share that same view after performing several traces and observing the RTT for all of the packets.  I don’t have any duplicate ack’s or retransmissions but I am still unable to explain why they believe they have a performance issue.

 

Any documentation explaining TDS would also be helpful.  I have done several traces and one of my problems is that it appears the customer is creating a long SQL query because I keep seeing packet too long for capture so the capture has been truncated messages in the info pane.  My interpretation with this is that the query was so large that it will take a large number of packets to return the data.  But how do I show this in the trace and how does TDS keep track of the number of packets ?  Also I can expand the TDS protocol in the detail pane but I don’t know how to interpret the fields after expanding. 

 

Any suggestions or other reading material would be greatly appreciated.

 

 

 

 

Kevin L. Gaudineer

Phone: (515)-241-7745

Cell:  (515)-205-3069

Email:  gaudinkl@xxxxxxx

 

 

 




         ********************************************

This message and accompanying documents are covered by the 
Electronic Communications Privacy Act, 18 U.S.C. Â§Â§ 2510-2521, 
and contain information intended for the specified individual(s) only. 
This information is confidential. If you are not the intended recipient 
or an agent responsible for delivering it to the intended recipient, you 
are hereby notified that you have received this document in error and 
that any review, dissemination, copying, or the taking of any action 
based on the contents of this information is strictly prohibited. If you 
have received this communication in error, please notify us immediately 
by e-mail, and delete the original message.

        *********************************************