Skip to Content.
Sympa Menu

freetds - Re: [freetds] DBD::Sybase not connecting - acts like it is not using FreeTDS

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] DBD::Sybase not connecting - acts like it is not using FreeTDS
  • Date: Fri, 15 Feb 2013 19:16:30 +0000

2013/2/15 James K. Lowden <jklowden AT freetds.org>:
> On Fri, 15 Feb 2013 09:24:44 -0600
> Darrell Cormier <solarisnut AT gmail.com> wrote:
>
>> The odd thing is that I copied these perl scripts directly from an
>> old server (configured in about 2005), which is still running these
>> scripts, and they still work well. I am wondering if there is a
>> slight change in the newer versions of DBD::SYBASE that are a little
>> more picky about the server designation.
>
> Hmm. Maybe. It could be that your query is now executed as a prepared
> statement, whereas in 2005 it would have been sent verbatim as plain
> SQL. If so, perhaps the server interprets the leading servername
> differently in that context.
>
> --jkl

As I remember if you specify the server in the table name the server
must be the name of the server or the name of a linked server. If you
copy the query to another machine which have a different server name
it complaints cause it does not found the table!

This was true even on mssql 2k. That's why you should not specify the
server name for local tables. Probably you where in the wrong database
and you used the table name only then you added the full name
(server.database.owner.tablename) and then when you switch server you
got the problem. If you changed tablename to database..tablename
(owner can be avoided) probably would be enough.

Frediano




Archive powered by MHonArc 2.6.24.

Top of Page