On Default Error Messages
It's not always wise to give too much information about something in the error message. I'm usually advocating giving as much information as possible, but not when you don't know what is wrong.
Case in point, the SqlConnection in .Net 2.0 will throw a message with this information:
The bolded part of the message is useful for the 5% cases, when you're using a SQL Server 2005 remotedly and it has not been opened to remote connections. In the other 95% of the time, it serves to confuse the user.
I had a connection string that was trying to connect to the wrong instance, and I got this message, so I started doing all the checks for connectivity, and it took a couple of minutes before I got actually read the connection string and fixed the instance name.
Comments
Comment preview