Groups | Blog | Home
all groups > sql server connect > april 2005 >

sql server connect : Understanding TDS


Craig Berntson
4/1/2005 2:57:22 PM
I'm trying to track down why some workstations are have performance
problems.

Both the "good" and "bad" workstations are running the same EXEs and using
the same MDAC rev. We're connecting with ADO to SQL Server 2000. Both are
connecting with Windows Authentication.

Looking at the network traces, the bad workstation is getting some TDS
packets that don't exist on the good workstation. I'm trying to find out
what would cause this. Under what conditions does the OLE DB Provider decide
to use TDS as opposed to not using it.

--
Craig Berntson
MCSD, Visual FoxPro MVP
www.craigberntson.com
Salt Lake City Fox User Group
www.slcfox.org
www.foxcentral.net


Mike Epprecht (SQL MVP)
4/2/2005 12:34:10 AM
Hi

TDS = Tabular Data Stream. It is SQL Server's on the wire protocol. It is
the only protocol is uses, that is then either encapsulated in Named Pipes,
TCP etc.

To be able to connect to SQL Server, any driver needs to implement TDS.

The best way to trace problems is to tell the server to use only one
protocol (it listens on Named Pipes and TCP by default). In the Server
network utility, only enable TCP (do not do this on a clustered SQL Server
unless you don't want it to work any longer). Some workstations might be
using Named Pipes and other not, giving different performance.

Regards
--------------------------------
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland

IM: mike@epprecht.net

MVP Program: http://www.microsoft.com/mvp

Blog: http://www.msmvps.com/epprecht/

[quoted text, click to view]

Craig Berntson
4/4/2005 9:42:27 AM
Both the "good" and "bad" workstations have TCP/IP, then Named Pipes listed
as the protocols in the Client Network Utility. My understanding is that the
protocols will be used in the order listed, unless it is unavailable.

The problem we're trying to trace down is slow performance on the "bad"
workstation. When we do a network trace on the "bad" workstation, it shows
TDS packets being transmitted, but those "TDS" packets don't exist on the
trace for the "good" workstation. I'm trying to understand why those packets
exist in some situations and not others.

We have tried running the "bad" workstation on just one protocol, but don't
see any performance increase.
--
Craig Berntson
MCSD, Visual FoxPro MVP
www.craigberntson.com
Salt Lake City Fox User Group
www.slcfox.org
www.foxcentral.net


[quoted text, click to view]

AddThis Social Bookmark Button