I've defined error message 60001, using sp_addmessage. An event has occurred in my stored procedure which
causes the following lines of my code to run
RAISERROR (60001, 16, 1) WITH SETERROR
On my (Database) side everything went according to plan - the process stopped and I have verified that
@@error contains 60001. Now
1. On the application developer's side (they'll be the ones calling the stored procedure) will they just
need to check to verify that @@error = 0 when the procedure terminates to know that the process was
2. On the database side, is there a way to see the current contents of the sysmessages table?
3. I know that state in an error message has no direct relevance to SQL server - has anyone found a
particularly good use for it?