SQL Server ERROR Messages explained: each has a number, a severity level and a state from 1 to 127, and all of them are stored in the sysmessages system table.
SQL SERVER – Fix : Error 1418 – Microsoft SQL Server – The server network address can not be reached
Error 1418 says the server network address cannot be reached or does not exist. Check the firewall, then enable TCP/IP for the server and client on port 1433.
SQL SERVER – Fix : Error: 18452 Login failed for user ‘(null)’. The user is not associated with a trusted SQL Server connection.
Error: 18452 Login failed for user ‘(null)’ means the server only allows Windows Authentication. Switch to Mixed Mode and enable the sa login to fix it.
SQL SERVER – Fix : Error 1702 CREATE TABLE failed because column in table exceeds the maximum of columns
Error 1702, CREATE TABLE failed, happens when a table goes past the 1024 column limit in SQL Server 2000. The fix is to cut the columns to 1,024 or fewer.
SQL SERVER – Fix : Error: 3902, Severity: 16; State: 1 : The COMMIT TRANSACTION request has no corresponding BEGIN TRANSACTION.
An SSIS package fails with Error 3902: the COMMIT TRANSACTION request has no corresponding BEGIN TRANSACTION. Two fixes, one is RetainSameConnection set to true.
SQL SERVER – 2005 – Explanation of TRY…CATCH and ERROR Handling
SQL Server 2005 brings TRY…CATCH for error handling, so you no longer check @@ERROR after every statement. Here is how the TRY and CATCH blocks work.
SQL SERVER – Fix: Server: Msg 7391, Level 16, State 1, Line 1
Msg 7391 has no single fix. I list the causes I have hit on my servers, from distributed transactions on linked servers to DTC firewall settings, to try one by one.