Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.albasani.net!eternal-september.org!feeder.eternal-september.org!.POSTED!not-for-mail From: Erland Sommarskog Newsgroups: comp.databases.ms-sqlserver,microsoft.public.sqlserver.programming Subject: Re: SSE 2008: Transactions and Rollbacks: When are they done? Date: Thu, 19 May 2011 23:38:29 +0200 Organization: Erland Sommarskog Lines: 19 Message-ID: References: <91q5t6h56vk3db1ipt8eacd5407jc08c7f@4ax.com> <9618t6ta7j80ptb76ko10h873g28v5dsmf@4ax.com> <91uat6d92cg68lk6472coa3okuque54tde@4ax.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Injection-Info: mx04.eternal-september.org; posting-host="DD6dU+BfJNjsjSP4/K/V7w"; logging-data="1076"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18NP8XrH81SLH88PlqWLaK1" User-Agent: Xnews/2006.08.24 Mime-proxy/2.1.c.0 (Win32) Cancel-Lock: sha1:/Xo3N//TNRPcvZSplul5tki/p98= Xref: x330-a1.tempe.blueboxinc.net comp.databases.ms-sqlserver:358 Gene Wirchenko (genew@ocis.net) writes: > It does not say why it normally does. I think the reason is that > a raiserror() with a severity >=11 triggers the catch block, but it is > not documented (that I can see). RAISERROR should invokes the CATCH block, so much is right. This is applies to both triggers and regular code. As for what is documented or not is this madhouse I don't know. I only know that the updated version of my article on error handling is long overdue... -- 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