SqlServer Instance listening on non-standard port

Report bugs and possible workarounds for ANSI TD versions
ivanmagalhaes
Canada
Posts: 2
Joined: 31 Mar 2021, 17:21
Location: toronto, canada

SqlServer Instance listening on non-standard port

Post by ivanmagalhaes » 18 Mar 2022, 11:49

We use connect strings in sql.ini

Not able to connect to Sql Server database listening on a non-standard port.

We have tried the following connecting strings
remotedbname=test,driver={SQL Server};server=TestServer,1455;QuotedId=No;AnsiNPW=No;database=TEST;
And
remotedbname=test,driver={SQL Server};server=TestServer,PORT=1455;QuotedId=No;AnsiNPW=No;database=TEST;

The port no. seems to be ignored.

Works when we create a DSN, but we need for it to works with a connect string.

fausto.lupercio
Ecuador
Posts: 157
Joined: 18 Sep 2017, 15:38
Location: Quito

Re: SqlServer Instance listening on non-standard port

Post by fausto.lupercio » 23 Mar 2022, 00:11

Hi.

I used in SQLServer:

Server,port

Example for port 21433 in SQLServer:

sConexion = "Server=192.168.1.88,21433;Database=BaseTest;User Id=sa;Password=sapass;"

Set bOk = SqlConnectDotNet (sqlH, sConexion , 'System.Data.SqlClient', DBP_PROVIDER_SQLSERVER_SQLCLIENT )

I hope you have a new idea.

Thanks.
Fausto.

a_sivababu
India
Posts: 501
Joined: 10 Mar 2017, 08:46
Location: Chennai,India

Re: SqlServer Instance listening on non-standard port

Post by a_sivababu » 23 Mar 2022, 06:25

Hi,
Is this Port issues for Win32 or .NET and what version it is.
if it is Win32 and want to bypass the SQL.Ini and ODBC then i think we need to wait as there is an issues but it works with 7.3.4 with Oneoff Patch. Refere Knowledge base document.

https://knowledge.opentext.com/knowledg ... KB17625098.

One more important thing,
Do not use SQL Server Driver as it is quite old and performance is very poor. Start using Microsoft ODBC Driver 17 as it is multiple times faster than this traditional driver and this will work even better if you use your database in Cloud. you might initially get some SQL error as SQL Server accepts even if the SQL is poorly designed.

If it is .NET, i think it should work as I have not faced any issues so far.

Thanks!
Sivababu A

Return to “Bug Reports (TD 4.2 and older)”

Who is online

Users browsing this forum: [Ccbot] and 0 guests