How to connect to SQL Server from LINUX - multi-instances.

[pnetti]

I am trying to setup the odbc.ini Address entry for a SQL Server connection. However there are multiple instances of sql server on the box.

I am told by others connecting to the database that the address is

Address=servername\inst2,1433

However this name does not work.

I get a message

DSR.MetaGeta(GET.TABLES)(SQLConnect('Siebeldb','SADMIN')): BCI Error:
SQLSTATE=0,CODE=11,[DataStage][SQL Client][ODBC][DataDirect][ODBC SQL Server Driver][libssclient20]
SQLSTATE=01000,CODE=11,[DataStage][SQL Client][ODBC][DataDirect][ODBC SQL Server Driver][libssclient20]ConnectionOpen (corptsql01\inst2,1433()).

Does anyone know how to setup the odbc.ini in this case?

[Ultramundane]

The others are connecting using datastage? I had a similar configuration and I had to disable named pipes for the named instance in order to get it to work. IBM nor datadirect could find the problem. Hopefully you will have same problem and workaround. If so, please report it to IBM.

[pnetti]

The others are connecting using datastage? I had a similar configuration and I had to disable named pipes for the named instance in order to get it to work. IBM nor datadirect could find the problem. Hopefully you will have same problem and workaround. If so, please report it to IBM.

[quote="How do I disable named pipes for the named instance? Is this something a server admin needs to do, or is this something that can be done within DataStage?[/quote]

[pnetti]

How do I disable named pipes for the named instance? Is this something a server admin needs to do, or is this something that can be done within DataStage?

[fkana]

Hi,

Did u solve this issue.

Faeez

[Ultramundane]

You disable named pipes for the sql server instance. So either your windows admin or your Sql server DBA will need to disable named pipes (if enabled). Make sure that the only protocol selected is tcp/ip.

Once they have done this hopefully you will be able to connect using:
Address=ServerAlias\SQLinstance

[pnetti]

I am being told by IBM that this problem has been corrected in the new 5.1 odbc drivers for REDHAT. There is also a set of 5.2 odbc drivers for REDHAT.

I will download/test and put the results in a reply.

[Ultramundane]

I was told that as well and they gave us the 5.2 drivers that had the fix. It still did not work and we had to do what I mentioned above. IBM nor datadirect were able to find the cause of the problem.

[BIuser]

added QEWSD=39001 it worked
[SQLServerdb]
Driver=/home/EMPIRE/dsadm/Ascential/DataStage/branded_odbc/lib/VMmsss20.so
Description=DataDirect SQL Server Wire Protocol
Database=Onyx
LogonID=sa
Password=sasybase
Address=SAONYX,1433
QuotedId=No
QEWSD=39001
AnsiNPW=No

[pnetti]

The problem is corrected in the odbc 5.1 drivers. I downloaded them from the IBM website.

The correct syntax for the Address entry is
Address=servername,port

Where the port number is the port of the target instance.

FYI: I also tested the 5.2 drivers but they did not work.

[Ultramundane]

There all multiple correct forms. For instance, this is also correct:
Address=ServerAlias\SQLinstance