home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!spool.mu.edu!agate!ucbvax!mtxinu!sybase!cosmo!davidvc
- From: davidvc@cosmo.sybase.com (David Van Couvering)
- Newsgroups: comp.databases.sybase
- Subject: Re: Network Protocol
- Message-ID: <27258@sybase.sybase.com>
- Date: 16 Dec 92 23:29:14 GMT
- References: <9212111843.AA15163@cs.columbia.edu>
- Sender: news@Sybase.COM
- Lines: 32
-
- In article <9212111843.AA15163@cs.columbia.edu>, li@cs.columbia.edu (Zhe Li) writes:
- |>
- |> Does anyone know which protocol is used to handle SQL batch commands
- |> transmission and related network requirements in Sybase? TCP/UDP or
- |> its own designed protocols? Anywhere to find more information about this?
- |>
- |> Thanks a bunch!
- |>
- |> --lee
- |> please email to: li@cs.columbia.edu
-
- Sybase uses its own published protocol called "Tabular Data Stream" or
- "TDS." This runs on top of the many different standard network
- protocols (e.g. TCP-IP, DecNet, etc.)
-
- I don't know how you can get your hands on the published specs for
- the TDS protocol -- your sales contact should be able to assist you
- with this.
-
- However, Open Client is the standard method of accessing the SQL Server;
- it is a (fairly) simple API that translates your requests into TDS
- sent over the network to the SQL Server. Results are then read back
- from the server in TDS; these results are translated and then made
- available via other Open Client API calls.
-
- Hope this helps,
-
- David
- --
- davidvc@sybase.com | {pacbell,lll-tis,pyramid,sun}!sybase!davidvc
- David Van Couvering Sybase 1650 65th Street Emeryville, CA 94608
- - Opinions expressed here are mine and not necessarily those of Sybase -
-