This post was formerly published at my beloved old blog "On the quest of a DBA's adventure......".
This is an old school stuff. I came across this system table named sysmessage when I exploring the system table set in a boring afternoon. This single table just opens up my eyes.
Every single possible error message (there are total 8901 error messages) from MS SQL Server that you can get, along with their error ID and its severity level in 11 different languages (like Japanese, Chinese, German,French and etc.). Wow, amazing. Any practical use? Not valuable to everyone, but I can think of one practical use.
Imagine, if you need to support overseas branched or campuses. Not every single individual can speak your language perfectly, after all Great Britain did never conquer the whole world so stop expecting everyone can speak English (it is like you want all programmer to code in C#). Also, server configuration in different country may end up error message in different languages.
While troubleshooting an application issue, your colleague has tried their best to translate what error message they received. Say they failed, they can't communicated with you. You could try to ask them for the error number for the error message. With this following query, say error id is 21:
It returned a list of the error in different languages. If you are lucky, you now know what they mean. OK, it is not "world-savingly" great, but it may be a little step forward to the solution at least.
No comments:
Post a Comment