Re^4: DBI and FreeTDS Named Instances

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?

Comment on Re^4: DBI and FreeTDS Named Instances

Replies are listed 'Best First'.
Re^5: DBI and FreeTDS Named Instances by dreadpiratepeter (Priest) on Aug 11, 2009 at 16:12 UTC
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]
Re^6: DBI and FreeTDS Named Instances by tux402 (Acolyte) on Aug 11, 2009 at 17:28 UTC
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^7: DBI and FreeTDS Named Instances by dreadpiratepeter (Priest) on Aug 11, 2009 at 20:42 UTC
Mine (which is working) has ServerName not Server in the odbc.ini, Also it it .odbc.ini on mine -pete "Worry is like a rocking chair. It gives you something to do, but it doesn't get you anywhere."	[reply]