Home > Articles > Programming > Windows Programming

Reasons for Using Both RETURN() and RAISERROR()

Author, consultant, and teacher Jimmy Nilsson suggests using both RETURN() and RAISERROR() for handling errors in stored procedures. Learn why in this short but powerful sample chapter.
This excerpt is derived from chapter 9 of .NET Enterprise Design with Visual Basic .NET and SQL Server 2000, by Jimmy Nilsson.
This chapter is from the book

You might think that I'm using both a safety net and a wire because I use both RAISERROR() and RETURN() of the error code when an error is encountered. I used to think so too, but this is still the best solution I'm aware of. First of all, the caller must be aware of an error so that it can take the correct action. For example, the caller probably shouldn't make another stored procedure call after an error, but should just go to the ExitHandler instead and end the stored procedure. Second, I want to have as much contextual information as possible for the logging solution.

Using RETURN() for communicating the result of a stored procedure is considered a de facto standard among T-SQL programmers. The RETURN() value can also be used from the .NET component, which would then know what went wrong, although the information will often be vague. For example, the following questions can't be answered:

  • Where in the call stack of the stored procedures did the error occur?

  • Which errors did the involved stored procedures raise from the error and "up" (that is, the error stack)?

  • Where in the stored procedure did the error occur?

This last question is an interesting one if the same error could occur in several places in one stored procedure, which is a common situation.

The other approach is to use RAISERROR() instead of RETURN(). This solves the problems concerning lack of context information. However, RAISERROR() introduces new problems in the context of stored procedures. There are two ways to use RAISERROR(). You can either use RAISERROR() with custom error codes (which means 50000 or higher, and the code must have been added in the sysmessages table), or you can use RAISERROR() with a string.

For example, assume that you catch the @@ERROR for a duplicate key (the duplicate key error code is 2627) and want to tell the calling stored procedure about the error. The problems you will encounter are

  • You can't raise that error to the caller because RAISERROR() may not use error codes of less than 50000.

  • If you put the error 2627 together with a description of where the problem is in a string and use that string with RAISERROR(), the caller stored procedure can't get to the string. Typically, the caller won't catch an error at all, but you can at least have that effect by using WITH SETERROR with RAISERROR() to give @@ERROR a value.

I could create new error codes by just adding 50000 to each one of those that already exists in sysmessages. I could then catch reserved errors, raise them again by taking their old value and adding 50000, and then use WITH SETERROR. (In this case, I would also have to add my custom error codes to sysmessages.) The advantage would be that I never have to check the return value of a stored procedure but only @@ERROR, but I find this technique to be clumsy and a bit of a hack. Thus, my conclusion remains to use both RETURN() and RAISERROR() and let them solve different problems, so to speak. This solution works very well, although I do have to check for both return values and @@ERROR after a stored procedure call.

Another reason for using RETURN() to communicate problems back to the components is that when SQL Server raises an error (such as 2627 because of duplicate keys, for example), it will be visible to the components as an exception, even if the stored procedure is prepared for the problem and handles it gracefully. In this case, the RETURN() will send 0 and the component knows that the exception can be skipped.


You can decrease the number of situations in which SQL Server raises errors that the component shouldn't see by taking proactive actions. Before you do an INSERT that you know might give a duplicate key error, you can check the situation with a SELECT first.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020