FreeTDS Development Group

[Jeff Dyson <jeff.dyson AT FRGrisk.com>]

Hello,

I am working on a Linux box that was previously configured with FreeTDS.  An 
IT admin has "proven" that the box can communicate with SQL Server by 
successfully connecting to the database with the tsql command.  My questions 
are - Does a successful tsql connection confirm that a FreeTDS ODBC driver is 
installed on the box?  If so, is there a way to determine which ODBC driver 
is in use by the tsql command?

I am new to FreeTDS.  I have read the FreeTDS User Guide but cannot find some 
of the files or directories referenced in the doc.  These missing items make 
me suspicious that the ODBC driver is not installed and that tsql does not 
require an ODBC driver.

For example:

*         There is no "freetds" directory on the box as referenced in the 
section about setting environment variables.

*         This "freetds" directory is also referenced in the DSN-less 
configuration section in the Driver= example for the odbcinst.ini file.

*         The driver named in the Driver= parameter is libtdsodbc.so.  My 
goal is to find this file, but it does not exist on the system.

*         There is no "unittests" directory as referenced in the Confirming 
the Installation.

My tsql command is as follows:
tsql -S sql83 -U userid -P password -D _database_

When run, I see the message "Default database being set to _database_".  If I 
run tsql with a bogus database name, I receive a 'Cannot open database...' 
message.  The sql83 server is defined in /usr/local/etc/freetds.conf.  The 
[sql83] entry identifies the host, the port, and the tds version (8.0).

The /etc/odbc.ini file as referenced in Chapter 4 is empty.

Given the above, is it possible that I am working with an incomplete FreeTDS 
installation?  Or at a minimum, is it possible that the ODBC drivers were 
omitted from the install?

Thanks for any thoughts or direction,
Jeff