http://www.perlmonks.org?node_id=1018376


in reply to Re^3: Connecting to sqlserver2008 - DBD::Sybase connectivity and unixODBC issue
in thread Connecting to sqlserver2008 - DBD::Sybase connectivity and unixODBC issue

The path in the odbcinst.ini file is an absolute path... i just removed it while posting here...sorry about that.. I am not sure if i have any documentation... As i am following up the process of DSN-less connection and ODBCINI file is not relevant here....Could you please provide me with more details...on how to implement this... Many Thanks

  • Comment on Re^4: Connecting to sqlserver2008 - DBD::Sybase connectivity and unixODBC issue

Replies are listed 'Best First'.
Re^5: Connecting to sqlserver2008 - DBD::Sybase connectivity and unixODBC issue
by mje (Curate) on Feb 12, 2013 at 14:53 UTC

    I can help with the ODBC setup, files etc (since I've written an ODBC driver and contributed to unixODBC) but I've never used the driver you are using. It looks like it needs something set up outside of normal ODBC (e.g. like an env var) but I cannot tell you what that is (e.g. with IBM's DB2 driver you have to DB2_INSTANCE env var or you get exactly the same error you are getting). Surely Microsoft have some docs to tell you what you need to do or perhaps the installer set something in your environment and you are logged in as someone else - just a guess. I'm surprised the installer did not create a driver section in your driver manager files for you.

      We are trying for all the possibilities for connectivity. Could you please give me any info regarding sybase interfaces file.... Also any links regarding the steps to be followed for achieving sql server connectivty from Perl. Thank you very much!!

        As I explained before, I don't use DBD::Sybase and the comment about the interfaces file was if you were connecting to Sybase - which I see you are not right now.

        You have completed all the steps I know about to connect to MS SQL Server as far as ODBC is concerned - the problem is your ODBC driver now. I've never used that ODBC driver and I believe the error is from the driver. The MS SQL Server ODBC driver I use is a commercial one my company sells.