Skip to Content.
Sympa Menu

freetds - Re: [freetds] FreeTDS on Debian: connect to MSSQL with ODBC fails

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: Frediano Ziglio <freddy77 AT gmail.com>
  • To: FreeTDS Development Group <freetds AT lists.ibiblio.org>
  • Subject: Re: [freetds] FreeTDS on Debian: connect to MSSQL with ODBC fails
  • Date: Tue, 11 Jan 2011 09:59:44 +0100

2011/1/11 Boniforti Flavio <flavio AT piramide.ch>:
> Hello Frediano and thanks for getting back to me.
>
>> > root@ticket:~# isql -v sqlexpress sa
>> > [S1000][unixODBC][FreeTDS][SQL Server]Unable to connect to
>> data source
>> > [37000][unixODBC][FreeTDS][SQL Server]Accesso non riuscito per
>> > l'utente 'sa'.
>> > [ISQL]ERROR: Could not SQLConnect
>> >
>>
>> Mmmm... "[FreeTDS]" means that unixODBC is loading and using
>> FreeTDS driver. On the other side "Accesso non riuscito..."
>> means that isql is actually connecting to a sql server (the
>> Italian error came from sql server). If tsql works this means
>> that odbc driver should connect (no ssl or tcp/ip protocol
>> problems). I don't know how isql works without a password but
>> try to pass password to isql like
>>
>> # isql -v sqlexpress sa your_password
>>
>> This has security impacts (anybody logged in the system while
>> executing isql command can read command line!) but for a test
>> in your personal machine this is not a problem.
>
> Indeed, it *is* working when passing my password!!! Look:
>
> root@ticket:~# isql -v sqlexpress sa password
> +---------------------------------------+
> | Connected!                            |
> |                                       |
> | sql-statement                         |
> | help [tablename]                      |
> | quit                                  |
> |                                       |
> +---------------------------------------+
> SQL>
>
> So, where may the problem lie?
>
> Thanks for helping me getting to this point.
>
> Flavio Boniforti
>

Well... the only problem I see is that not passing password to isql
cause an empty password to be used which (correctly) server refuse.
So... you get the connection, you can issue commands (you can try with
a "select @@version") and everything is working :)

Now... get to next step... PHP/Perl/whatever/C... I don't know... :)

freddy77




Archive powered by MHonArc 2.6.24.

Top of Page