Unable to connect to the named instance

[Stan-RED]

I have multiple named instances (different MSSQL versions) installed on the same host, e.g. "localhost\SS2022". When trying to use instance name as a server for secret or directly in the connection as it usually works in other clients, I have a Cannot resolve hostname 'localhost\SS2022' error. Without named instance it can't connect due to the timeout error.

[VGSML]

Yes, this is not implemented yet. Technically the named instance is a normal SQL Server instances that works on the same machine with different tcp ports. Often this ports is dynamic defined by instance startup. SQL Server on windows provides the separate service that can return current port for the named instance.
I will work on the integrated security (NTLM/Kerberos) and this will the part of the task.

[VGSML]

For now you can define a constant port for the SQL Server instances and attach it directly to the duckdb