Path: csiph.com!usenet.pasdenom.info!gegeweb.org!eternal-september.org!feeder.eternal-september.org!mx04.eternal-september.org!.POSTED!not-for-mail From: Erland Sommarskog Newsgroups: comp.databases.ms-sqlserver Subject: Re: SSE2008: #Tables, Stored Procedures, Avoiding ActiveX Date: Wed, 01 Aug 2012 23:27:06 +0200 Organization: Erland Sommarskog Lines: 29 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Injection-Info: mx04.eternal-september.org; posting-host="9c1143bfab35549403b85d70ea1a57d8"; logging-data="783"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19VkpViM7Y8JzFK7XodGA/x" User-Agent: Xnews/2006.08.24 Mime-proxy/2.1.c.0 (Win32) Cancel-Lock: sha1:mJJUxUKEyLd7WYTZ9qeWXC55XvU= Xref: csiph.com comp.databases.ms-sqlserver:1208 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