Author: Peter Whyte

Every Windows-authenticated connection to SQL Server uses one of two schemes, and most teams could not say which without looking. That is usually fine, right up until a linked server double-hop fails, a security baseline starts restricting NTLM, or an SSPI error appears and nobody knows what “normal” looked like. This post is the five-minute…

🚨Part of the SQL Server Errors series, the exact messages and what actually causes them. Msg 229  ·  Level 14  ·  State 5 The SELECT permission was denied on the object ‘RlsOrders’, database ‘DemoDatabase’, schema ‘dbo’. Msg 229, Level 14, State 5 ⚡The message already names object, schema and database. Look for a DENY before…

🚨Part of the SQL Server Errors series, the exact messages and what actually causes them. OS error 53  ·  Named Pipes Provider  ·  error 40 Named Pipes Provider: Could not open a connection to SQL Server [53]. A network-related or instance-specific error has occurred while establishing a connection to SQL Server. The server was not…

🚨Part of the SQL Server Errors series, the exact messages and what actually causes them. Msg 17806  ·  Level 20  ·  State 14 SSPI handshake failed with error code 0x8009030c, state 14 while establishing a connection with integrated security; the connection has been closed. Msg 17806, Level 20, State 14 ⚡Clock first: five minutes of…

🚨Part of the SQL Server Errors series, the exact messages and what actually causes them. Msg 2627 / 2601  ·  Level 14  ·  State 1 Violation of PRIMARY KEY constraint ‘PK_ErrDemoPk’. Cannot insert duplicate key in object ‘dbo.ErrDemoPk’. The duplicate key value is (1). Msg 2627, Level 14, State 1 ⚡Half of these are replayed…

🚨Part of the SQL Server Errors series, the exact messages and what actually causes them. Msg 916  ·  Level 14  ·  State 2 The server principal “ErrDemo916” is not able to access the database “DemoDatabase” under the current security context. Msg 916, Level 14, State 2 ⚡Check the database, not the login: the named database…