key to db error code meaning?

tbh
Open an ERROR.LOG to see what is going on? Deadlocks?
"tbh" <femdev@.newsgroups.nospam> wrote in message
news:OypijxhbIHA.1208@.TK2MSFTNGP03.phx.gbl...
> on a server running SQL Server 2000 we occasionally get errors. the most
> frequent ones in a recent profiler trace, for example, are 208 and 1205.
> i've been searching in vain for an explanation of what these mean. i found
> a key to severity, but not to the meaning of the errors themselves. can
> someone please point me to a guide on the subject?
> cheers,
> Tim Hanson
>
The generic error messages are in master.dbo.sysmessages. E.G.,
Select * From master.dbo.sysmessages Where error = 208
But when you actually get the errors, SQL Server will pass back a string as
well as the error message. This string will have the parameters replaced
with actual values. For example, error 208 is invalid object name, but when
you actually get the message, it will tell you which object name was
invalid. But if whatever connection method you are using is swallowing the
error text and only returning the error number, you can look it up in
sysmessages. You can also search on it in BOL. BOL doesn't have every
error, but it gives additional info about some of them.
Tom
"tbh" <femdev@.newsgroups.nospam> wrote in message
news:%23g3a4iibIHA.4144@.TK2MSFTNGP05.phx.gbl...
> thanks. i was thinking more in terms of a table of definitions. i can find
> hints, e.g., for error 208:
>
> http://www.novicksoftware.com/TipsAndTricks/tip-sql-server-replication-208.htm
> thought maybe there is a summary of error message meanings (or range
> categories) along the lines of what I found for "severity".
> the ones we get appear to be routine. there isn't much in the ERROR.LOGs.
> thanks again,
> tbh
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:eAQscEibIHA.536@.TK2MSFTNGP06.phx.gbl...
>