Re: DBD::Sybase not connecting - acts like it is not using FreeTDS
Frediano Ziglio <[email protected]>
| Newsgroups | gmane.comp.db.tds.freetds |
|---|---|
| Message-ID | <CAHt6W4ce1gW9PZi=TMG7zntbZ-Xx0cwZ3+9X6wGTY8NJQ89EOA@mail.gmail.com> |
2013/2/15 James K. Lowden <[email protected]>: > On Fri, 15 Feb 2013 09:24:44 -0600 > Darrell Cormier <[email protected]> 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