Wireshark-bugs: [Wireshark-bugs] [Bug 3098] New: MS SQL 2005 tds protocol support

From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Fri, 5 Dec 2008 15:48:30 -0800 (PST)

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3098

           Summary: MS SQL 2005 tds protocol support
           Product: Wireshark
           Version: unspecified
          Platform: PC
        OS/Version: Windows Server 2003
            Status: NEW
          Severity: Major
          Priority: High
         Component: TShark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: aaghili@xxxxxxxxxxxxxxxxxx


Created an attachment (id=2537)
 --> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=2537)
2 captures see above 

Build Information:
Paste the COMPLETE build information from "Help->About Wireshark", "wireshark
-v", or "tshark -v".
--
Hi I'd like to request support for MS SQL 2005 tds protocl. 2 capture files
with the issue.

In mssql.txt there are 2 captures. In the first query you can't see the pay
load or the table name. In the 2nd you can see part of the payload but its
truncated. 

The most important issue is that you can't see the actual query that's being
made. It says Select but the sql query is not there. 

In other db protocols like mysql  wireshark dissects the packet in a way that
can see the query.

Guy Harris wrote:
> On Dec 5, 2008, at 12:30 PM, Al Aghili wrote:
> 
>> Yea it looks like MS SQL Server 2005 is not fully supported. I just  
>> ran
>> a test with it. In some cases you can see the query and the result
>> coming back but in other cases you can't see either. Do you know if
>> there is plan to support MS SQL 05 in the future? It's really close,
>> just not consistent.
> 
> There aren't "official" plans to support any protocol in Wireshark;  
> support happens when somebody decides to add it:
> 
> 	http://www.wireshark.org/faq.html#q1.11
> 
> Now that Microsoft appear to be documenting it, it might be easier to  
> fix issues with it, although we might need captures with problems in  
> order to fix the problems (and probably would need them to test the  
> fixes).
> _______________________________________________

Can you supply a not too large capture ??

If so, probably the best way is to open an enhancement request 
(bugs.wireshark.org) and attach the capture.


-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.