Home > Sql Server > Catch Error In Sql Server 2008 Stored Procedure

Catch Error In Sql Server 2008 Stored Procedure


Print this Article. IF ERROR_NUMBER() IS NULL RETURN; -- Return if inside an uncommittable transaction. -- Data insertion/modification is not allowed when -- a transaction is in an uncommittable state. Here is an outline of such a procedure may look like: CREATE PROCEDURE error_demo_cursor AS DECLARE @err int, ... If your procedure might be called by programmers in a different town in a different country, you need to take extra precautions. have a peek here

IF XACT_STATE() <> 0 BEGIN ROLLBACK TRANSACTION; END EXECUTE dbo.uspLogError @ErrorLogID = @ErrorLogID OUTPUT; END CATCH; -- Retrieve logged error information. But if you have procedure which only performs updates to the database, this option gives some performance improvement by discarding the rows affected messages. If the statement results in an error, @@error holds the number of that error. You can just as easily come up with your own table and use in the examples.

Try Catch In Sql Server 2008 Stored Procedure Example

Copy USE AdventureWorks2008R2; GO -- Verify that the stored procedure does not already exist. Here I only mention one: sp_xml_removedocument, which returns 1 in all situations, so for this procedure you should only check @@error (I believe Microsoft has acknowledged this as a bug.) For declare @t table (i int);declare @RC int;exec @RC = test;insert into @t values (@RC);select * from @t; works fine. –Martin Smith Feb 6 '13 at 21:16 @MartinSmith . .

Copy USE AdventureWorks2008R2; GO BEGIN TRY -- This PRINT statement will run because the error -- occurs at the SELECT statement. Cannot insert duplicate key in object 'dbo.sometable'. This can happen either because there is a BEGIN TRANSACTION without a matching COMMIT or ROLLBACK TRANSACTION being executed, or because an error causes SQL Server to abort execution of the Sql Server 2008 Stored Procedure Output Parameter This type of error will not be handled by a TRY…CATCH construct at the same level of execution at which the error occurred.

SELECT @err = @@error IF @err <> 0 RETURN @err SELECT col1, col2, ... Sql Server 2008 Stored Procedure Transaction Try Catch Did this Avatar: The Last Airbender character die? CREATE PROCEDURE usp_GetErrorInfo AS SELECT ERROR_NUMBER() AS ErrorNumber ,ERROR_SEVERITY() AS ErrorSeverity ,ERROR_STATE() AS ErrorState ,ERROR_LINE () AS ErrorLine ,ERROR_PROCEDURE() AS ErrorProcedure ,ERROR_MESSAGE() AS ErrorMessage; GO -- SET XACT_ABORT ON will cause What Was "A Lot of Money" In 1971?

View all articles by Robert Sheldon Related articles Also in BI Relational Algebra and its implications for NoSQL databases With the rise of NoSQL databases that are exploiting aspects of SQL Sql Server 2008 Stored Procedure If Statement Take what I present in this article as recommendations. Conditional tests for IF and WHILE. ListDensityPlot of a data set in polar coordinates I have some overlapping troubles in my diagram Did Maul correctly state this character's secret identity?

Sql Server 2008 Stored Procedure Transaction Try Catch

As you can see we are using a basic SELECT statement that is contained within the TRY section, but for some reason if this fails it will run the code in Consider this very stupid example: CREATE TABLE stray_trans_demo (a int NOT NULL) go CREATE PROCEDURE start_trans AS BEGIN TRANSACTION go CREATE TRIGGER stray_trans_trigger ON stray_trans_demo FOR INSERT AS EXEC start_trans go Try Catch In Sql Server 2008 Stored Procedure Example You’ll be auto redirected in 1 second. Sql Server 2008 Stored Procedure Error Handling Best Practices ERROR_NUMBER.

It is worth noting that using PRINT in your CATCH handler is something you only would do when experimenting. navigate here My recommendation is to set the timeout to 0 which means "no timeout", unless you have a clear understanding what you want to use the timeout for. The return value doesn't get inserted there anyway. Note: the syntax to give variables an initial value with DECLARE was introduced in SQL2008. Sql Server 2008 Stored Procedure Return Value

The CATCH block must not perform any actions that would generate writes to the log if XACT_STATE returns a -1. As a result, the stored procedure now generates an error, which is shown in Listing 9. 12345  (0 row(s) affected)Actual error number: 547Actual line number: 9Msg 50000, Level 16, State 0, You just need to be sure that any of your roll back/clean up is not going to create more errors and that whatever you are trying to clean up, is malleable http://completeprogrammer.net/sql-server/catch-error-in-sql-server-2008.html The RAISERROR statement comes after the PRINT statements.

SELECT * FROM dbo.ErrorLog WHERE ErrorLogID = @ErrorLogID; GO Nested Error-handling ExampleThe following example shows using nested TRY…CATCH constructs. Sql Server 2008 Stored Procedure Input Table Variable Get started Top rated recent articles in Database Administration Azure SQL Data Warehouse: Explaining the Architecture Through System Views by Warner Chaves 0 SQL Server Access Control: The Basics by This means that TRY…CATCH constructs can be placed inside other TRY and CATCH blocks.

Instead let's first look at the SELECT statement inside of it: SELECT @errmsg = '*** ' + coalesce(quotename(@proc), '') + ', Line ' + ltrim(str(@lineno)) + '.

GOTO can also be used to exit a TRY block or a CATCH block; however, GOTO cannot be used to enter a TRY block or a CATCH block.Error-Handling Solution in the With this setting, most errors abort the batch. Copy BEGIN TRY BEGIN TRY SELECT CAST('invalid_date' AS datetime) END TRY BEGIN CATCH PRINT 'Inner TRY error number: ' + CONVERT(varchar,ERROR_NUMBER()) + ' on line: ' + CONVERT(varchar, ERROR_LINE()) END CATCH Sql Server 2008 Stored Procedure Lock Icon Some of these considerations, I am covering in this text.

Also, the original error numbers are retained. If I'm traveling at the same direction and speed of the wind, will I still hear and feel it? Error Handling with User-Defined Functions If an error occurs in a user-defined function (with the exception of table-valued inline functions), this is very difficult for the caller to detect. this contact form In itself this is not likely to affect the continued processing, but it is a token of that something has already gone wrong, why it is best to back out, so

This documentation is archived and is not being maintained. But it is also important to check the manipulation of the temp table before the transaction starts, because if any of these operations fail, the INSERT, UPDATE and DELETE in the Copy BEGIN TRANSACTION; BEGIN TRY -- Generate a constraint violation error. Here, I will only point out one important thing: your reaction to an error raised from SQL Server should always be to submit this batch to avoid orphaned transactions: IF @@trancount

Required fields are marked with an asterisk (*). *Name *Email Notify for updates *** NOTE *** - If you want to include code from SQL Server Management Studio (SSMS) in your The answer is that we don't want to continue execution after an error, because we are likely to have incorrect data, and thus it is likely that the execution will yield Copy -- Verify that the stored procedure does not already exist. On the next line, the error is reraised with the RAISERROR statement.