Open jmakov opened 6 months ago
Same issue here. I believe it is caused by incorrect handling of connection string when connecting to a specific instance of SQL server. In you case server = "192.168.254.254\\MYSQLINSTANCE1"
and database = 'MYDB1'
, MYSQLINSTANCE1
is not parsed correctly.
@wangxiaoying This is an ongoing issue that has been reported several times. Is it something you will look into?
@lyngc SQL server uses instance mechanism as kind of proxy for inbound port 1433 to relay it to a port that corresponds to actual instance. You can find "instance" port by running:
USE master
GO
xp_readerrorlog 0, 1, N'Server is listening on', N'any', NULL, NULL, N'asc'
GO
and then connect to the server:port
without specifying instance.
It is sort of workaround until the issue with parsing of connection string is fixed.
@lyngc SQL server uses instance mechanism as kind of proxy for inbound port 1433 to relay it to a port that corresponds to actual instance. You can find "instance" port by running:
USE master GO xp_readerrorlog 0, 1, N'Server is listening on', N'any', NULL, NULL, N'asc' GO
and then connect to the
server:port
without specifying instance. It is sort of workaround until the issue with parsing of connection string is fixed.
But the port will change when the instance restarts. Hope this will be fixed soon. But it seems like MSSQL is not highest priority.
What language are you using?
Python
What version are you using?
0.3.2
What database are you using?
mssql
What dataframe are you using?
Polars
Can you describe your bug?
Establishing a connection with
pyodbc
works, times out withconnector-x
What are the steps to reproduce the behavior?
Database setup if the error only happens on specific data or data type
Not applicable
Example query / code
What is the error?