From: esquel@sommarskog.se   
      
   Gene Wirchenko (genew@ocis.net) writes:   
   >      Huh?  Of course it involves updates.  I do not want bad data   
   > getting into the database.  That is the point of the error checks.   
   >   
   >      Did you misstate, or am I missing some context here?   
      
   The example you posted was a retrieval procedure. I can only work   
   from the code I see, not the code I don't see.   
      
   >      Do you mean that your input table gets modified with the result?   
   > Something like:   
   >           SomeKey     }   
   >           Data1       } Process   
   >           Data2       } this.   
   >           Data3       }   
   >           ProcessingStatus           } What happened   
   >           ProcessingErrorMessage     } goes here.   
      
   Yup. These are typicall background processes of some sort. In many cases   
   there is data coming from an external source, and this data needs to   
   be validated, as it could have errors.   
      
   --   
   Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se   
      
   Links for SQL Server Books Online:   
   SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx   
   SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)