FreeTDS Development Group

[Brian Bruns <camber AT ais.org>]

I think there is a bit of confusion here.  I'd suggest reading
http://msdn.microsoft.com/library/psdk/sql/ba_highprog_56pc.htm

It seems our friends at Microsoft have introduced a new protocol version,
8.0,  although they continue to support 4.2 and 7.0.  The changes from 
7.0 -> 8.0 seem to be mainly the 64bit 'bigint' type and column level
collations, whatever that is.  If someone wants to send me network traces
of a TDS 8 conversation, I'll see about implementing it.

So, in theory there should be no problem using FreeTDS or FreeTDS/JDBC
with SQL Server 2000.  Of course there may be existing bugs tickled by the
new server version ;-)  

Remember ODBC is a API not a protocol.  Whether you access SQL Server
through ODBC, OLE-DB, MS DbLib, JDBC, or FreeTDS, it's all TDS on the
wire.

Brian

On Fri, 16 Mar 2001, Marco Wijtkamp wrote:

> At 13:09 16-3-01 -0800, you wrote:
> >Thanks for your response, but I do not understand your answer.
> >
> >What is ctlib? Why does it work with a few comuns, but not when I have more
> >than 13 columns?
> >
> >Is there a work-around?
> 
> I am afraid that there is no work-around. In basic there are two way to 
> connect. Thru ODBC (that's what Bill wants) and directly to the middleware 
> using an API call from / to libraries. The last option is, due the absence 
> of the extra ODBC layer, much faster and stable but not available in 
> sqlserver 2000. Microsoft simply isn't backwards compatible in this case. 
>