FreeTDS Development Group

["Lowden, James K" <LowdenJK AT bernstein.com>]

> From: NZQCOUMXWJFZ AT spammotel.com [mailto:NZQCOUMXWJFZ AT spammotel.com]
> Sent: February 27, 2003 10:19 AM
> 
> >> I look into the dump-file of 
> >> freetds.log I cannot find the database name... what can I do 
> >> to get the connection working:
> 
> > I think ASA is interpreting the lservname field of the 
> > login packet, which
> > normally carries the servername, as a database name. The 
> > TDS 5.0 spec says:
> >
> > This field SHOULD correspond with the
> > @@servername of the server for best results.
> > [...]
> > For Adaptive Server Anywhere this field indicates
> > the name of the database which the connection
> > should be made to (the database must
> > already be loaded). If the name in this field
> > doesn't match any currently loaded database the
> > connection silently ends up in the "default"
> > database.
> 
> Okay. It works. I made a small change to freetds.conf:
> 
> BEFORE:
> [FAMSQL]
>         host = FAMSQL
>         port = 2638
>         tds version = 5.0
> 
> AFTER:
> [FAMADMIN]
>         host = FAMSQL
>         port = 2638
>         tds version = 5.0
> 
> Which means that the name in the square brackets stands for the 
> DB-name!!!! Hell!
> Thanks a lot for this hint.

You're welcome.  I like to be right.  ;-)

To be very clear: the "name in the square brackets" *is* the servername.
For some reason known only to Sybase, ASA [mis]interprets the login packet.
Every other TDS 5.0 server recognizes lservname as the servername, but ASA
expects it to be the database name.  What you did is make the servername the
same as the database name.  

As things stand, you need a separate entry in freetds.conf for every ASA
database.  I suppose that's OK, but I think it would be nearly as easy to
fix as to document and support the current situation.  I don't have ASA
available though, so I'd need a guinnea pig.  

> What really astonishes me, that no one else had this problem (I was 
> searching the web for 2 days for an answer) - a hint in the 
> manual on this 
> Sybase problem would be fine / and or in the 
> /usr/share/doc/freetds/README(.Debian) or the example confs.

On a positive note, you just added to our store of knowledge on the subject!


I agree.  The thing is, we see 1000 questions about Microsoft servers for
every one about ASA; I don't think that's much of an exaggeration.  Support
for ASA crept into FreeTDS pretty recently, and Brian is the only one among
the developers who has a copy.  What you're doing, then, is relatively rare
and relatively new.  For instance, the port information found its way into
the user guide only in the last year.  

I think I can find a place for a footnote in the UG for 0.61, though.  

Regards, 

--jkl


The information contained in this transmission may contain privileged and
confidential information and is intended only for the use of the person(s)
named above.  If you are not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient, any
review, dissemination, distribution or duplication of this communication is
strictly prohibited. If you are not the intended recipient, please contact
the sender immediately by reply e-mail and destroy all copies of the
original message. Please note that we do not accept account orders and/or
instructions by e-mail, and therefore will not be responsible for carrying
out such orders and/or instructions.