FreeTDS Development Group

["Brian Bruns" <camber AT ais.org>]

Dollars to donuts, it's the driver setting these options.  However there
is a "library" field in the TDS protocol for identifying which API is in
use.  So, theoretically SQL Server could discriminate among clients.  It'd
be foolish, but possible. So,

> "When an ODBC application
> connects ... the server automatically sets...."

could mean that the server sets the options in response to requests by the
client (driver). Splitting hairs but it is the server that controls these
things in the end.

Brian

> Hmmm...  Interesting.  I found this in my SQL Server 7.0 Books Online help
> file (I searched for 2147483647, which turned up 23 matches -- this is from
> the section entitled "Effects of SQL-92 Options").  It seems to indicate
> that the ODBC driver issues these statements, not the server.
> 
>     When the SQL Server ODBC driver connects to SQL Server version
>     7.0, the server detects that the client is using the ODBC driver
>     and sets several options on. The options set on by SQL Server 7.0
>     are the same as those turned on by SET statements when the driver
>     connects to SQL Server 6.5, except that SQL Server 7.0 also sets
>     on the CONCAT_NULL_YIELDS_NULL option.
> 
>     ...
> 
>     The driver issues these statements itself; the ODBC application
>     does nothing to request them. Setting these options allows ODBC
>     applications using the driver to be more portable because the
>     server behavior then matches the SQL-92 standard.
> 
> And this from the "SET TEXTSIZE (T-SQL)" page"
> 
>     The SQL Server ODBC driver and Microsoft OLE DB Provider for
>     SQL Server automatically set TEXTSIZE to 2147483647 when
>     connecting.
> 
> 
> It's intersting to me that these 2 references state that the _driver_ issues
> these commands, not the _server_.  If this were really the case, would we
> see the odd behaviour we do with TEXT?  Perhaps 2147483647 is the default as
> well as maximum size no matter what client.