March 22, 2016 at 12:05 pm
A remote Sybase query is causing some issues which 'supposedly' was working before. In tracing IO and execution plan I get the following results
Table 'Worktable'. Scan count 2, logical reads 1842878, physical reads 0, read-ahead reads 0, lob logical reads 0, lob physical reads 0, lob read-ahead reads 0.
Table 'MAP_SUBSCRIBER_RESIDENT'. Scan count 2, logical reads 6, physical reads 0, read-ahead reads 0, lob logical reads 0, lob physical reads 0, lob read-ahead reads 0.
Table 'MAP_SUBSCRIBER_LOCATION'. Scan count 2, logical reads 6, physical reads 0, read-ahead reads 0, lob logical reads 0, lob physical reads 0, lob read-ahead reads 0.
Client statistics
Wait time on server replies117895
Bytes sent from client 3408
Bytes received from server3172
I am trying to resolve the high 'worktable' IO which seems to indicate large volumes of data being received and bytes received from server which seems manageable. I am seeing 40% waitstats of preemptive_com_getdata but am not sure if that is relevant.
Any suggestions on where to look?
Viewing post 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy