[freetds] FreeTDS and Ubuntu, iodbc
mohnd at egolfscore.com
Tue Apr 17 16:11:29 EDT 2007
On strike? They must be under-appreciated then.
/usr/local/freetds/bin/bsqlodbc -S dsn=eGolfScore Prod;uid=xxx;pwd=xxx
and a couple of other variants, but am still getting;
[FreeTDS][SQL Server]Unable to connect to data source
However, I decided to try something with iodbctest. I connected to the
above dsn with iodbctest. Then I did a select * from a table with about
1000 rows, it returned the data. I did the select again, but this time
after it started spitting stuff back, I pulled the network plug. After
waiting bout 20 minutes, it still had not responded back. My
FreeTDS.conf has timeout set to 10.
So can I assume that FreeTDS is not communicating back to iodbc with the
timeout error? If not, should I test with bsqlodbc, or would that test
be the same? Or could it be a configuration issue, even though I can
connect ok via iodbctest and my application?
I just want to note I appreciate all your help so far with this.
On Mon, 2007-04-16 at 21:34 -0400, James K. Lowden wrote:
> Dan Mohn wrote:
> > I tried bsqlodbc, which when I just type the command tells me it
> > the same parameters as bsqldb, but it results in;
> > /usr/local/freetds/bin/bsqlodbc -S <ip address> -U <user> -P
> > -D <database> -i timeouttest.sql
> > bsqlodbc: error -1: SQLConnect: SQL_ERROR: failed
> > "[FreeTDS][SQL Server]Unable to connect to data source"
> Hmm. I see there's no man page either. I wonder if the documentation
> staff went on strike?
> The bsqlodbc -S option takes a DSN name the way other ODBC utilities
> not an ip address or a freetds.conf dataserver name. Sorry that
> clear. Thanks for sticking with it.
More information about the FreeTDS