SqlException.Number one value but two different documentations. How?

user_12667080 0
Viewed 124

I am trying to implement fault tolerance and trying to collect a list of SQL error numbers that are considered transient. but I keep running into error numbers that have multiple documentations.

Consider error number 10053:

(1) A transport-level error has occurred when receiving results from the server (from here)

(2) Could not convert the data value due to reasons other than sign mismatch or overflow. (from here)

It gets weirder. Consider error number 11001:

(1) Non-NULL value successfully returned.

(2) An error has occurred while establishing a connection to the server....

Both from the same Microsoft docs page adjacent to each other.

What's going on?

azure-sql-database sql-server
1 Answers

As @Jeroen Mostert said,
Error 10053 means that an established connection has been dropped.

  • An established connection was aborted by the software in your host machine.
  • The TCP/IP Connection was aborted by Windows. This was possibly due to a data transmission timeout or protocol error.
  • The virtual circuit was terminated due to a time-out or other failure. The application should close the socket as it is no longer usable.

SQL server error 11001 occurs when the SQL Server can't be found on Network. This happens if the IP address is not reachable or the TCP port number is either not open or is not the correct port number or is blocked by a firewall

  • This error mainly occurs when the SQL Server client can't connect to the server. This may happen when the client cannot resolve the name of the server or the name of the server is incorrect.

So we should check firewall list in Azure sql first.

user_139794870
Related