Skip to Content.
Sympa Menu

freetds - Re: [[freetds] Re: Re: RE: freeTDS unixODBC...Which one isn't working]

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "James K. Lowden" <jklowden AT schemamania.org>
  • To: FreeTDS Development Group <freetds AT lists.ibiblio.org>
  • Subject: Re: [[freetds] Re: Re: RE: freeTDS unixODBC...Which one isn't working]
  • Date: Tue, 6 Jan 2004 00:47:43 -0500

On Tue, 06 Jan 2004, Steven Orton <sorton9999 AT usa.net> wrote:
> "Daughterson, Adam [EPM/BOU/MMI]" wrote:
>
> > Thanks again to everyone that has helped. What wound up eventually
> > working was pointing isql at an older database hosted on an older box.
> > The
> > production database is run from a Windows2003 server, we think that
> > the security may have changed, because I have no issues (now :-))
> > connecting to the older database running on a Windows2000 server.
> > Both DB's are run from MSSQL servers, the newer is MSSQL2000, I think
> > the older is running on MSSQL7.
>
> that opens up a potential problem for my project then. we plan on
> upgrading
> to SQLServer2000 in the near future. i may ping on you guys for some
> gotchas, things i should know, etc. so you don't really think this is
> resolved, do you?

Let's not start any rumors. :-)

There are some minor differences between versions 7 and 8 of the TDS
protocol, and any 8.0 server will talk to a 7.0 client. There are some
subtleties with named pipes and such when setting up domain logins. But
by and large FreeTDS doesn't have any problem talking to SQL Server 2000,
or, for that matter, 2003. No more so than it has with SQL Server 7.0,
that is. ;-)

I'm not sure we quite explained what was going on with Adam's setup, but
it's clear there were several variables, and let's not forget that he had
tsql working all along.

--jkl




Archive powered by MHonArc 2.6.24.

Top of Page