Re: Sql server + DBI package + freetds module = problem :)

Replies are listed 'Best First'.
Re^2: Sql server + DBI package + freetds module = problem :) by alex452 (Novice) on Jan 25, 2007 at 15:15 UTC
here is what i see from my test script above ----------------- DBI connect('server=212.247.84.54:1433;database=JACKPOT','sa',...) failed: OpenClient message: LAYER = (6) ORIGIN = (8) SEVERITY = (5) NUMBER = (3) Server 212.247.84.54:1433, database Message String: ct_connect(): directory service layer: internal directory control layer error: Requested server name not found. at alextest11.pl line 4 Cannot connect to database: OpenClient message: LAYER = (6) ORIGIN = (8) SEVERITY = (5) NUMBER = (3) Server 212.247.84.54:1433, database Message String: ct_connect(): directory service layer: internal directory control layer error: Requested server name not found. --------------	[reply]
Re^3: Sql server + DBI package + freetds module = problem :) by derby (Abbot) on Jan 25, 2007 at 15:45 UTC
Specifying an ip address and port number is not the normal way to connect to a Sybase (or MSSQL) database ... check out the "Connecting to Sybase" section of DBD::Sybase - especially the "interface file" section. -derby Update: Following my own advice, you can bypass the interface files by specifying host and port in the DSN: `$dbh = DBI->connect( "dbi:Sybase:host=db1.domain.com;port=4100", $user, $passwd);` [download]	[reply] [d/l]
Re^4: Sql server + DBI package + freetds module = problem :) by alex452 (Novice) on Jan 25, 2007 at 16:54 UTC
Hi again, Thanks for trying to help guys, Derby, unfortunately the port nr did nothing, i tried, the same result. The problem is, i am now sure of it is that freetds is not used by DBI module. trying to modify SYBASE env variable to point to freetds.conf leads to error messages about missing sybase files like config/objectid.dat	[reply]
Re^5: Sql server + DBI package + freetds module = problem :) by Anonymous Monk on Oct 12, 2011 at 02:56 UTC


Think about Loose Coupling
	PerlMonks