FreeTDS Development Group

["Sharad Bansal" <sharad AT ITAngel.com>]

Hi,

The reason why I think that option is not optimal is speed and
maintainence. This will be an ultra-high performance prop database. And,
I rather have Microsoft optimize OLEDB. If I can program the server to
talk TDS, then you can even use SQL query analyzer to access our
database.

Is there a master list of various TDS message formats ? Or, tds.h the
only source for that?

Thanks.

-----Original Message-----
From: James K. Lowden [mailto:jklowden AT schemamania.org] 
Sent: Thursday, August 01, 2002 7:09 AM
To: TDS Development Group
Cc: sharad AT ITAngel.com
Subject: Re: [freetds] TDS implementation on windows: using OLDEDB to
access proprietary database

On Wed, 31 Jul 2002 15:08:50 -0400, "Sharad Bansal" <sharad AT ITAngel.com>
wrote:

> I am building a proprietary database on the windows platform and want
to
> allow microsoft clients connect to it using OLEDB. As I understand,
for
> this to happend I need to make sure that the prop database talks TDS
> format and responds to queries from clients just like microsoft SQL
> server does.

Sharad, 

If I understand you correctly, your database and clients are on a
Microsoft platform, and you want the clients to use OleDB to access the
database.  

You don't need TDS to do that.  You "just" write an OleDB provider with
VC++.  The OleDB Tables and Accessors in OleDB will be the means by
which
your clients access the data in your proprietary database.  The client
(normally written in VB) then opens your database in much the same way
it
would open an ODBC data source; the database may be local or elsewhere
on
the network.  

Microsoft wrote an "OleDB provider" interface to SQL Server.  I think
our
documentation might say that their OleDB interface is "just another
client
library", but on reflection I think that's not true.  AFAIK, we have no
evidence that the OleDB provider uses TDS, nor any reason to think it
would.  Their provider lives on the server; it is accessed by a local
client via DCOM.  

Regards, 

--jkl