Login | Register   
LinkedIn
Google+
Twitter
RSS Feed
Download our iPhone app
TODAY'S HEADLINES  |   ARTICLE ARCHIVE  |   FORUMS  |   TIP BANK
Browse DevX
Sign up for e-mail newsletters from DevX


Tip of the Day
Language: Enterprise
Expertise: Beginner
Nov 30, 2001

Consistent Error Handling in SQL Server


Suppose you need to tack on an additional value to all your custom errors in SQL Server 2000. For VB programmers, that might mean tacking on the value of vbobject error to all SQL errors in order to remain consistent throughout your application. To do this, you'll need to create a User Defined function called vbobject error:
 
CREATE FUNCTION vbObjectError
-- Input custom Error number
   (@CustomError int )
RETURNS bigint --
AS
BEGIN
-- this will make a positive number so as to be _
compadable with SQL Server
-- When it returns, you'll need to make it negative _
again
   RETURN ((-2147221504 +  @CustomError)*-1)
END

Then, you need a centralized error handling routine:
 
Create a stored proc called RaiseCustom Error -

CREATE procedure dbo.RaiseCustomError
	(
	@ErrNumber	int
	)
As
SET NOCOUNT ON

Declare @ErrorNumber bigint

Set @ErrorNumber = dbo.vbObjectError(@ErrNumber);

Raiserror(@ErrorNumber, 15, 1);
GO

Finally, you can call your errors from any stored procedure:
 
exec raisecustomerror 6302
Thomas Messina
 
Comment and Contribute

 

 

 

 

 


(Maximum characters: 1200). You have 1200 characters left.

 

 

Sitemap
Thanks for your registration, follow us on our social networks to keep up-to-date