While I know why are ports used in SQL Server, I wonder what is the difference between an endpoint and a port. Ports can be managed using Configuration Manager, is it also possible to manage endpoints with CM?
Thanks for your time.
SQL Server – Difference Between Endpoint and Port
configuration-managerNetworksql serverterminology
Related Question
- Sql-server – How Should TCP/IP be configured to allow an external application access to SQL via the same port #
- SQL Server – Connect Without Specifying Port
- Sql-server – Unable to connect to SQL Server 2016 remotely
- SQL Server – Dynamic Ports Setting Issues
- SQL Server – How to Identify Default Instance in Configuration Manager with Changed Port Number
- Sql-server – Access SQL Server Configuration Manager on a remote server
- SQL Server – Secure and Unsecure Traffic Configuration
Best Answer
I like to think of it as the endpoint being the "SQL Server side" part of what a client connects to. There are endpoints for TCP (probably the one you refer to), Named Pipes and Shared Memory. Those are the regular endpoints that a client application connects to. You can, for instance, set privileges on an endpoint, allowing login A to connect to TCP and B connect to Shared Memory (not that I've ever had the need for this). The endpoint is implemented by a DLL (I usually refer to all this as "NetLib", and for TCP and Named Pipes exposed through a port.
Then there are endpoints for mirroring and the old SOAP web-methods as well.