In this post, I am sharing a small and useful demonstration for printing a Stored Procedure name in the CATCH block of SQL Server.

SQL Server developers are using TRY CATCH block in their Stored Procedures, but if they print Stored Procedure name in the CATCH block, it is easy to identify a particular stored procedure error from the error log files.

It is also beneficial for an application developer to determine the name of the stored procedure with an error.
We can use ERROR_PROCEDURE() to print a stored procedure name in the CATCH block.

Below is a small demonstration on this:

Create a sample stored procedure:

CREATE PROCEDURE usp_SampleErrorProc  
AS  
    PRINT 'Sample message...'
	SELECT 1/0;  
GO

Execute above sample stored procedure:

BEGIN TRY  
    EXECUTE usp_SampleErrorProc  
END TRY  
BEGIN CATCH  
    SELECT 'Procedure_Name: ' + ERROR_PROCEDURE() AS ErrorProcedureName;  
END CATCH;  
GO

As a DBA, I also defined the database coding standard in my organization in which I also created template for TRY – CATCH block.

For few old projects, we are still working on SQL Server 2008, but after SQL Server 2012, I had to change the format of TRY – CATCH block.
SQL Server 2012 introduced the new form of CATCH block which I am using now for all new projects where we are using SQL Server 2014/2016.

Below is a comparison between the New CATCH and Old CATCH:

The old approach of CATCH:

BEGIN TRY
	DECLARE @n AS INT;
	SET @n = 7/0
END TRY
BEGIN CATCH
	DECLARE @message NVARCHAR (4000)
	DECLARE @severity INT
	DECLARE @state INT

	SELECT @message = ERROR_MESSAGE ()
	SELECT @severity = ERROR_SEVERITY ()
	SELECT @state = ERROR_STATE ()

RAISERROR (@message,@severity,@state)
END CATCH

Error message in result:

Msg 50000, Level 16, State 1, Line 14
Divide by zero error encountered.

The new approach of CATCH:

BEGIN TRY
	DECLARE @n AS INT
	SET @n = 7/0
END TRY
BEGIN CATCH
	THROW
END CATCH

Error message in result:

Msg 8134, Level 16, State 1, Line 3
Divide by zero error encountered.