Re: TDS vs. TCP

I'm using "Ethereal". I start capturing the network traffic between SQL
Server and the client. The communication between SQL Cluster instance and
the client, I don't see any TDS packets but the communication between SQL
stand-a-lone server and the client, I see TDS packets.

Ayad

"Linchi Shea" <LinchiShea@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:82135502-5B49-4C8A-A6C4-27C22A487429@xxxxxxxxxxxxxxxx
I was trying to understand how you 'see' TDS or TCP packets. What tool did
you use to 'see' TDS packets or TCP packets?

Linchi

"Ayad" wrote:

That's true in stand-a-lone server but in Cluster where SQL is a Virtual
Host, I only see TCP packets.

That's what I'm trying find out why? When I ran a query against
stand-a-lone
SQL instance, I see both TDS and TCP packets where in the TDS packets the
query and the respose to it, BUT in cluster I don't see any TDS packets,
only TCP.

Ayad


"Linchi Shea" <LinchiShea@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1E34769C-8395-4B6F-B37F-4044D6B8740F@xxxxxxxxxxxxxxxx
What I found, when I point the client to test server, I see TDS
packets
between the client and Test SQL server but when I point it to
production
(cluster), I see only TCP packets (no TDS packest).

Can you clarify what you meant by 'see TDS' or 'see only TCP"? SQL
Server
speaks TDS between client and server, and the trasport can be TCP. In
other
words, TDS packets would be payload on TCP packets. So you should "see"
both
all the time (if TCP is the transport).

Linchi

"Ayad" wrote:

Hi,

I have 2 SQL 2000 Ent. instance, one is stand alone (test) and the
other
instance is on Cluster (production) (W2K3).

I have an application perfomance issue, the application runs ok on
test
but
it is slow on production. I took a network capture for both instances
and
anlyzed the communication between the client and SQL servers.

What I found, when I point the client to test server, I see TDS
packets
between the client and Test SQL server but when I point it to
production
(cluster), I see only TCP packets (no TDS packest).

Does this make any sense?

Thanks

Ayad








.

Relevant Pages

  • Re: Diagnose co-location networking problem
    ... it was from the client. ... Actually there's significant indication of lost packets and clues that ... 540 retransmit timeouts ... are you using any packetfiltering on the server? ...
    (freebsd-net)
  • Re: DataSet.GetChanges() in RowChanged(DataRowAction.Add)
    ... have you considered SQL Express and use ... > I realize now that I didn't describe well how the client application is ... > Framework installed on the client machine, but not any SQL Server). ... > 20 tables in different relations with eachother in the database, ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: SBS 2003 and Sql Server ~ Client Install
    ... I've found the client tools and have now successfully installed them. ... Access front end to a SQL database, Excel can be a front end, A word mail merge document could access a SQL database via ODBC. ... We are trying to install the client software. ... We understand that a Northwind training database is available for SQL Server. ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: process stuck in nfsfsync state
    ... >> server is wedged, not the client. ... Comparing the client and server traces, it looks like fragments in the ... loss for individual packets adds up. ...
    (freebsd-stable)
  • Re: SBS 2003 and Sql Server ~ Client Install
    ... I've found the client tools and have now ... A word mail merge document could access a SQL database via ... We want to install to gain an understanding. ... Once we've managed to install the SQL Server Client we can start to ...
    (microsoft.public.backoffice.smallbiz2000)