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.
SQL SERVER – Fix: HResult 0x274D, SQLCMD Level 16, State 1 Error: Microsoft SQL Native Client : Login timeout expired
SQLCMD error HResult 0x274D, Microsoft SQL Native Client: Login timeout expired? TCP/IP is off by default in SQL Server 2005; enable it in Configuration Manager.
SQL SERVER – TempDB is Full. Move TempDB from one drive to another drive.
When TempDB is Full, I investigate capacity and usage before moving its files. A move requires a planned restart.
SQL SERVER – Fix : Error 8101 An explicit value for the identity column in table can only be specified when a column list is used and IDENTITY_INSERT is ON
Error 8101 means you gave a value for an identity column. What IDENTITY_INSERT does, why there are two different errors, and why TRY CATCH misses it.
SQL SERVER – Fix : Error 701 There is insufficient system memory to run this query
For Error 701, insufficient system memory, compare max server memory with min server memory, check the paging file size, and free caches with DBCC commands.
SQL SERVER – Fix: Error Msg 128 The name is not permitted in this context. Only constants, expressions, or variables allowed here. Column names are not permitted.
Msg 128, The name is not permitted in this context, shows up when one column is used as the DEFAULT of another. Use only constants, expressions or variables.
SQL SERVER – SQL Commandments – Suggestions, Tips, Tricks
My 20 SQL Commandments for SQL Server, rewritten from an Oracle article: know your data, test with realistic data, write identical statements, and more tips.