in reply to Re^2: DBI and FreeTDS Named Instances
in thread DBI and FreeTDS Named Instances

in that case the issue is going to be a configuration issue with freetds. It took me forever to get it right. remember that you have to configure the servers in freetds.conf and the dbs in the .odbc.conf file in the home directory of the user running the code.


-pete
"Worry is like a rocking chair. It gives you something to do, but it doesn't get you anywhere."

Replies are listed 'Best First'.
Re^4: DBI and FreeTDS Named Instances
by Anonymous Monk on Aug 11, 2009 at 14:29 UTC
    Ok, I think I understand the config files. It's unfortunate that this has become less portable because of that. Would you happen to have an example dsn that uses the config file? Or does freetds automatically look at the file if the dsn is missing information?
[reply]

      I believe you need to setup the config files regardless of what you pass into the DSN

      You need an entry in the freetds.conf for each server and an entry in the .odbc.conf for each database



      -pete
      "Worry is like a rocking chair. It gives you something to do, but it doesn't get you anywhere."
[reply]
        Here is a copy of my config files. 
        odbc.ini
[ODBC Data Sources]
VOIP
[VOIP]
Driver = FreeTDS
Description = Connection to the new voip DB
Trace = No
Server = 127.0.0.1
Port = 4433
Database = databasename
[Default]
Driver = FreeTDS

freetds.conf
[VOIP]
host = 127.0.0.1
instance = CRSSQL
port = 4433
client charset = UTF-8
tds version = 8.0

odbcinst.ini
[FreeTDS]
Description = FreeTDS Driver
Driver = /usr/local/lib/libtdsodbc.so
Setup = /usr/lib/odbc/libtdsS.so

        [download]

        Does anything look off?
[reply]
[d/l]
Re^4: DBI and FreeTDS Named Instances
by Anonymous Monk on Aug 11, 2009 at 14:30 UTC
    ^ oops, didn't log in before I posted.
[reply]

In Section Seekers of Perl Wisdom