Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Capturing The Error Description In A Stored Procedure Expand / Collapse
Author
Message
Posted Thursday, April 22, 2004 2:48 PM


SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Tuesday, September 03, 2013 6:05 AM
Points: 847, Visits: 48
Comments posted to this topic are about the content posted at http://www.sqlservercentral.




--
Amit



"There is no 'patch' for stupidity."



Download the Updated SQL Server 2005 Books Online.
Post #112659
Posted Wednesday, April 27, 2005 5:24 PM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, April 08, 2014 2:13 PM
Points: 188, Visits: 421

To catch those elusive error messages you could also try:

Declare @SQL nVarChar(4000)
Set @SQL=N'osql -Usa -P -Q"declare @t table(PKey Int not Null) insert @t select Null"'
Exec xp_CmdShell @SQL

and do whatever you want with the response





PeteK
I have CDO. It's like OCD but all the letters are in alphabetical order... as they should be.
Post #178126
Posted Monday, November 19, 2007 6:40 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, June 12, 2013 8:36 AM
Points: 12, Visits: 103
Amit, excellent posting!!!!

I am in same kind of situation.. by setting Xact_abort off you are loosing transaction control.

BTW, I could not able to find your code snippet.

Can you please forward to me at my email.... jagadeeswar.bomma@gmail.com

Thanks



jay
Post #423559
Posted Tuesday, April 29, 2008 12:19 PM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Friday, March 21, 2014 1:49 PM
Points: 317, Visits: 158
Another alternative follows. Note that the error message contains details such as
the parameter values at the time of error and the name of the stored procedure
(or you could refer to a section of SP). You might also consider adding details
like the userid.

The point of this is to show that you CAN get error details out of a stored procedure,
even though the default return value is only an INT datatype. The example shows a
raiserror and a print of the error message - in some cases you may want to raise the
error within a stored procedure, while at other times you may want to handle it
outside the SP, such as the print statement that could have just as easily handed
the error message to your calling code or to a logging process.


IF EXISTS (SELECT * FROM dbo.sysobjects
WHERE id = OBJECT_ID(N'[dbo].[usp_errorhandling]')
AND OBJECTPROPERTY(id,N'IsProcedure') = 1)
DROP PROCEDURE [dbo].[usp_errorhandling]
GO
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
--------------------------------------------------------------------
--Purpose: Error handling example
--Changes:
-- Bill Nye 4/29/08 Created
--------------------------------------------------------------------
CREATE PROCEDURE [dbo].[usp_errorhandling]
@Branch int ,
@Division int ,
@errormsg varchar(1000) output
AS
SET NOCOUNT ON
DECLARE @errorid int

Select 1/0 -- Purposely cause error
Set @errorid=@@Error
IF @errorid <> 0
BEGIN
SELECT @errormsg=description FROM master.dbo.sysmessages
WHERE error=@errorid
SET @errormsg='Error updating when Division_ID='
+ Cast(@Division as char(1)) + ' and Branch_ID='
+ Cast(@Branch as varchar(3)) + ' in usp_errorhandling: '
+ @errormsg
RAISERROR(@errormsg,16,1)
END

GO
-------------------------------

DECLARE @RC Int, @errormsg varchar(1000)
EXEC @RC = [dbo].[usp_errorhandling] 999, 9, @errormsg OUTPUT
Print @errormsg
Print @rc

GO

DROP PROCEDURE [dbo].[usp_errorhandling] -- Cleanup

Post #492406
Posted Thursday, October 30, 2008 10:31 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, January 13, 2009 7:03 AM
Points: 3, Visits: 10
Hi Amit

I tried to download your code attached with this topic, But it doesn't work.
Will you please check it and email me your code, that will be great.
tahirmd@hotmail.com

Regards
Post #594527
Posted Friday, November 07, 2008 1:34 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, January 13, 2009 7:03 AM
Points: 3, Visits: 10
Thanks Amit

Using your Idea I'm able to solve "Capturing The Error Description In A Stored..." for SQL 2000.

I would like to share my investigation with you guys.

Here are my findings:-
With this query I'm trying to create duplicate records in pubs.dbo.authors. By calling SP I get SQL error message.

USE [PUBS]
GO

INSERT INTO authors
values('172-32-1176','Doe','Jone','408-496-7223','Bigge Rd.','Menlo Park','CA','94345',1)

DECLARE @retval INT
EXEC usp_Get_ErrorMessage @retval output

Results:
[errNumber: 2627] [errState: 1] [errLevel: 14] [errInstance: MyLocal] [errLine: 1] [errProcedure: NULL] [errMessage: Violation of PRIMARY KEY constraint 'UPKCL_auidind'. Cannot insert duplicate key in object 'authors'.]

(1 row(s) affected)

Note:- Store procedure "usp_Get_ErrorMessage" is attached with this thread. rename .txt with .sql

Best of Luck
Logician --> [Tahir]


  Post Attachments 
usp_Get_ErrorMessage.txt (19 views, 9.12 KB)
Post #599267
Posted Tuesday, January 13, 2009 3:02 AM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Friday, February 08, 2013 7:25 AM
Points: 443, Visits: 48
Bill,

Many of the sysmessage strings contain placeholders that should be fed variables run-time. Extracting the string only will produce messages like this:

"Cannot insert the value NULL into column '%.*ls', table '%.*ls'; column does not allow nulls. %ls fails."

Essential information about which column and which table is missing.

Sincerely,
Lasse
Post #635242
Posted Monday, January 20, 2014 7:26 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, February 03, 2014 12:03 PM
Points: 1, Visits: 14
Thanks Pete!
Post #1532834
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse