SQL Server cannot start TCP port occupancy

Scene Reproduction:

--------------------------------------------------------------------------------------------------------------- ---------------------------------

The first step:

View Windows Logs

Step Two:

See which shameless program is taking up 1433 ports

You can see that this process is 5164 occupied,

Step Three:

In Task Manager, kill the process with number 5164, and grab the port. So TCP is available! Complete.

------------

If you don't use TCP/IP, you can tell SQL Server not to turn on! Let it voluntarily abandon this TCP/IP port.

So that you don't grab a port with someone else, you don't report an error, so you can turn on SQL Server. Note that this

TCP/IP is not available, which means that SQL Server does not receive network packets.

------------

Workaround 2: Do not start TCP first

Step 1: Run Sqlserver_configuration_manager

Step 2: Disable TCP/IP

SQL Server cannot start TCP port occupancy