RE: MS SQL Server 2000

I tried all the steps in Freetds "Is server there ?"

% ping -c1 CCR23MSG2F08
PING CCR23MSG23F08 (172.18.57.150): 56 data bytes
64 bytes from 172.18.57.150: icmp_seq=0 ttl=128 time=40.057 ms

--- CCR2MSG23F08 ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max = 40.057/40.057/40.057 ms

% telnet CCR23MSG2F08 1433
Trying 172.18.57.150...
Connected to CCR2MSG2F08.
Escape character is '^]'.

% pwd
/dev/fs/C/SFU/usr/examples/freetds-0.62.dev.20030410

% cd src/apps

% ./tsql -H CCR23MSG2F08 -p 1433 -U freetds
locale is "POSIX:POSIX:POSIX:POSIX:POSIX:POSIX"
charset is "ASCII"
Password:
Segmentation fault (core dumped)  

What could be wrong this time? 

After going thru the below mail I have given right entries in freetds.conf
file.


[CCR2MSG2F08]
        host = 172.18.57.150
        port = 1433
        tds version = 7.0
        try server login = yes


Any clue would be of great help.
TIA
Swapna


-----Original Message-----
From: Lowden, James K [mailto:LowdenJK@xxxxxxxxxxxxx] 
Sent: Thursday, February 27, 2003 9:28 PM
To: 'FreeTDS Development Group'
Subject: RE: [freetds] MS SQL Server 2000

> From: Akshay Rao [mailto:Akshay@xxxxxxxxxxx]
> Sent: February 27, 2003 10:39 AM
> 
> So I assume that my freetds.conf file should look something like this:
> 
> [SQL2K]
>       host = XXX.XXX.XXX.XXX
>       port = XXXX
>       tds  = 8.0
> 
> Is that correct?  

"SQL2K" would be the servername, the name your application uses to connect
to the named instance.  For people who have several instances on one
machine, sanity might best be preserved if the freetds.conf servername
corresponds to the server's instance name.  

"host" should be the DNS hostname of the machine running "SQL2K".  Don't use
the address; let DNS do its job.  

"port" would be the port where the named instance is listening.  

TDS version 7.0 or 8.0 should work.  No reason not to use 8.0 that I know
of.  

> I also read about some options such as "try domain login",
> "try server login", "nt domain", and "emulate little endian". 
>  Should I be
> concerned with these options?

One (and only one) of either "try domain login" or "try server login" must
be "yes".  If the login is defined in SQL Server, use "try server login".
If the login is defined in the NT domain, use "try domain login".  

I'm not aware of any outstanding Endian issues.  AFAIK, even big endian
clients don't need "emulate little endian" anymore.  

--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.


_______________________________________________
FreeTDS mailing list
FreeTDS@xxxxxxxxxxxxxxxxx
http://lists.ibiblio.org/mailman/listinfo/freetds
************************************************************************** 
This email (including any attachments) is intended for the sole use of the
intended recipient/s and may contain material that is CONFIDENTIAL AND
PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or
distribution or forwarding of any or all of the contents in this message is
STRICTLY PROHIBITED. If you are not the intended recipient, please contact
the sender by email and delete all copies; your cooperation in this regard
is appreciated.
**************************************************************************