Comments on: Sql Server Error 18456: Login Failed http://bobondevelopment.com/2007/12/13/sql-server-error-18456-login-failed/ Musings on the craft and business of software development Thu, 26 Aug 2010 03:21:57 -0600 http://wordpress.org/?v=2.8.6 hourly 1 By: Aaron Davis http://bobondevelopment.com/2007/12/13/sql-server-error-18456-login-failed/comment-page-1/#comment-3430 Aaron Davis Fri, 14 Dec 2007 14:42:53 +0000 http://bobondevelopment.com/2007/12/13/sql-server-error-18456-login-failed/#comment-3430 Man, MS really do not understand helpful error message. How hard would it have been to tack a description at the end of the log entry. I am glad that they have error codes, severity, state and the like, because that can be used to gain additional information (i.e. easier to search for on google). But diskspace is cheap, and a couple dozen extra characters in a log entry is not going to fill it that much faster. I can't decide if it is laziness or incompetence, but this seems to exemplify their attitude toward error reporting. (Although it's not as bad as "Catastrophic Failure" in Visual Studio). Man, MS really do not understand helpful error message. How hard would it have been to tack a description at the end of the log entry.

I am glad that they have error codes, severity, state and the like, because that can be used to gain additional information (i.e. easier to search for on google). But diskspace is cheap, and a couple dozen extra characters in a log entry is not going to fill it that much faster.

I can’t decide if it is laziness or incompetence, but this seems to exemplify their attitude toward error reporting. (Although it’s not as bad as “Catastrophic Failure” in Visual Studio).

]]>