freetds AT lists.ibiblio.org
Subject: FreeTDS Development Group
List archive
- From: "Lowden, James K" <LowdenJK AT bernstein.com>
- To: "'FreeTDS Development Group'" <freetds AT lists.ibiblio.org>
- Subject: RE: [freetds] MS SQL Server 2000
- Date: Thu, 27 Feb 2003 10:57:31 -0500
> From: Akshay Rao [mailto:Akshay AT crc.ufl.edu]
> 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] MS SQL Server 2000,
Akshay Rao, 02/26/2003
- <Possible follow-up(s)>
- RE: [freetds] MS SQL Server 2000, ZIGLIO Frediano, 02/26/2003
-
RE: [freetds] MS SQL Server 2000,
Lowden, James K, 02/26/2003
- RE: [freetds] MS SQL Server 2000, Daniel Morgan, 02/26/2003
-
RE: [freetds] MS SQL Server 2000,
Lowden, James K, 02/26/2003
- RE: [freetds] MS SQL Server 2000, Daniel Morgan, 02/26/2003
-
RE: [freetds] MS SQL Server 2000,
Bort, Paul, 02/26/2003
- RE: [freetds] MS SQL Server 2000, Daniel Morgan, 02/26/2003
- RE: [freetds] MS SQL Server 2000, Akshay Rao, 02/27/2003
-
RE: [freetds] MS SQL Server 2000,
Lowden, James K, 02/27/2003
- RE: [freetds] MS SQL Server 2000, Brian Bruns, 02/27/2003
- RE: [freetds] MS SQL Server 2000, Lowden, James K, 02/27/2003
Archive powered by MHonArc 2.6.24.