Error when running SQL Server ‘Default’ instance on a non default TCP port

preview_player
Показать описание
Running SQL Server ‘Default’ instance on a non-default (or non-standard) TCP port.
The result is that the SQL Server client won't look for the browser service and will attempt to connect to 1433.
This results in being unable to connect to default instance and the resolving of the instance port not taking place even in Microsoft management studio

There is the option to change the client to resolved is see MS Blog post.

Follow us on
Рекомендации по теме
Комментарии
Автор

Is it anyhow possible to connect sql instance with non default port on remote machine without specifying port no?

abhaymohite