How to configure ODBC connection to SQLServer using dynamic ports in IBM Information Server

-
​

Question

SQLServer is setup to dynamically assign ports. In the .odbc.ini file, the Address parameter is usually set to hostname colon port number (Address=HostName:1433), but the port may change. How should we handle this?

Answer

For the Address parameter value, instead of entering the hostname colon port, enter the hostname a backslash and the server instance name.

For example, in Unix/Linux, use the IBM SQLServer Wire Protocol driver and enter the following in the .odbc.ini file in the DSN definition for the connection to the SQLServer data source:

Address=HostName\Server_Instance_Name

For Windows, use the ODBC Data Sources Administrator to configure a System DSN for the data source using the IBM SQLServer Wire Protocol driver.

Note: The parameter is Server

​

Popular posts from this blog

Shrink you container size up to 95%.

-
BLAFS is a bloat-aware filesystem for container debloating. The design principles of BLAFS are effective, efficient, and easy to use. It detects the files used by the container, and then debloats the container by removing the unused files. The debloated containers are still functional and can run the same workload as the original containers, but with a much smaller size and faster deployment. https://github.com/negativa-ai/BLAFS?tab=readme-ov-file
Read more

alma linux: dnf Module yaml error: Unexpected key in data

-
While applying recent updates to a server running Rocky Linux 8, an error presented itself. Module yaml error: Unexpected key in data: static_context [line 9 col 3] Module yaml error: Unexpected key in data: static_context [line 9 col 3] The solution turned out to be a simple one. Update the libmodulemd first to correct the problem then perform the dnf updates as usual. dnf update libmodulemd For a detailed explanation as to the cause of this problem.
Read more