Comments on: SQL SERVER – Introduction to SQL Error Actions – A Primer http://blog.sqlauthority.com/2012/04/26/sql-server-introduction-to-sql-error-actions-a-primer/ Personal Notes of Pinal Dave Fri, 17 May 2013 15:26:57 +0000 hourly 1 http://wordpress.com/ By: SQL SERVER – Weekly Series – Memory Lane – #026 | SQL Server Journey with SQL Authority http://blog.sqlauthority.com/2012/04/26/sql-server-introduction-to-sql-error-actions-a-primer/#comment-464710 Sat, 27 Apr 2013 01:32:07 +0000 http://blog.sqlauthority.com/?p=18365#comment-464710 [...] Introduction to SQL Error Actions – A Primer [...]

]]> By: ralph@mrocrib.com http://blog.sqlauthority.com/2012/04/26/sql-server-introduction-to-sql-error-actions-a-primer/#comment-335033 Tue, 21 Aug 2012 17:50:31 +0000 http://blog.sqlauthority.com/?p=18365#comment-335033 Column function (B){var a=this.indexOf(B);if(a!=-1){this.splice(a,1)}return this} must be set

]]> By: SQL SERVER – 5 Videos from Joes 2 Pros Series Exam Prep Series 70-433 – SQL in Sixty Seconds « SQL Server Journey with SQL Authority http://blog.sqlauthority.com/2012/04/26/sql-server-introduction-to-sql-error-actions-a-primer/#comment-322729 Wed, 01 Aug 2012 01:31:59 +0000 http://blog.sqlauthority.com/?p=18365#comment-322729 [...] Most people believe that when SQL Server encounters an error severity level 11 or higher the remaining SQL statements will not get executed. In addition, people also believe that if any error severity level of 11 or higher is hit inside an explicit transaction, then the whole statement will fail as a unit. While both of these beliefs are true 99% of the time, they are not true in all cases. It is these outlying cases that frequently cause unexpected results in your SQL code. [Detailed Blog Post] [...]

]]> By: SQL SERVER – SQL in Sixty Seconds – 5 Videos from Joes 2 Pros Series – SQL Exam Prep Series 70-433 « SQL Server Journey with SQL Authority http://blog.sqlauthority.com/2012/04/26/sql-server-introduction-to-sql-error-actions-a-primer/#comment-284951 Wed, 16 May 2012 01:30:55 +0000 http://blog.sqlauthority.com/?p=18365#comment-284951 [...] [Detailed Blog Post] | [Quiz with Answer] [...]

]]> By: SQL SERVER – Quiz and Video – Introduction to SQL Error Actions « SQL Server Journey with SQL Authority http://blog.sqlauthority.com/2012/04/26/sql-server-introduction-to-sql-error-actions-a-primer/#comment-283414 Thu, 10 May 2012 01:30:54 +0000 http://blog.sqlauthority.com/?p=18365#comment-283414 [...] is follow up blog post of my earlier blog post on the same subject - SQL SERVER – Introduction to SQL Error Actions – A Primer. In the article we discussed various basics terminology of the error handling. The article further [...]

]]> By: jalpesh vadgama http://blog.sqlauthority.com/2012/04/26/sql-server-introduction-to-sql-error-actions-a-primer/#comment-281424 Wed, 02 May 2012 16:02:35 +0000 http://blog.sqlauthority.com/?p=18365#comment-281424 Nice Job Pinal!! You are becoming full time writer

]]> By: ChiragSatasiya http://blog.sqlauthority.com/2012/04/26/sql-server-introduction-to-sql-error-actions-a-primer/#comment-279833 Thu, 26 Apr 2012 14:30:48 +0000 http://blog.sqlauthority.com/?p=18365#comment-279833 Hi pinal sir,
Thank you for a simple and informative explanation.
Specially those image explain everything.

Regard$
Chirag Satasiya

]]> By: jerik1 http://blog.sqlauthority.com/2012/04/26/sql-server-introduction-to-sql-error-actions-a-primer/#comment-279706 Thu, 26 Apr 2012 06:59:38 +0000 http://blog.sqlauthority.com/?p=18365#comment-279706 Dear Dave, you write: SQL Server will now choose which errors are drastic enough to fail an entire stored procedure (or batch) – under XACT_ABORT OFF.

Are there any rules the decisions are made?

]]> By: Anuj Bhardwaj http://blog.sqlauthority.com/2012/04/26/sql-server-introduction-to-sql-error-actions-a-primer/#comment-279692 Thu, 26 Apr 2012 05:54:01 +0000 http://blog.sqlauthority.com/?p=18365#comment-279692 BEGIN TRY

Statements 1
.
.
.
END TRY
BEGIN CATCH
IF @@TRANCOUNT > 0
ROLLBACK

END CATCH

In try catch block, the next statement will be executed after error occurred.

]]>