RE: RaisError in Database Pro
- From: jialge@xxxxxxxxxxxxxxxxxxxx ("Jialiang Ge [MSFT]")
- Date: Fri, 11 Jul 2008 06:06:14 GMT
Hello Dave,
Would you please let me know the severity level in your RAISEERROR
statement? The severity level is defined in the second parameter. For
example:
RAISERROR('Ten Most Expensive Products did not return 10 rows',11,1)
In the above statement, the severity level is 11.
In TSQL, only when severity level is higher than, or equal to 11 will it be
regarded as an error. Severity levels lower than 11 are regarded as
"informational" or "warning" and will be ignored:
below 11: are warnings, not errors
11-16: are available for use
above 16: are system errors
Based on my tests, when severity level is lower than 11, the database unit
testing won't fail. Dave, please check whether this is the case on your
side, and let me know the result if you increase the severity level of
RAISEERROR.
Regards,
Jialiang Ge (jialge@xxxxxxxxxxxxxxxxxxxx, remove 'online.')
Microsoft Online Community Support
=================================================
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msdnmg@xxxxxxxxxxxxxx
This posting is provided "AS IS" with no warranties, and confers no rights.
=================================================
.
- Follow-Ups:
- RE: RaisError in Database Pro
- From: "Jialiang Ge [MSFT]"
- RE: RaisError in Database Pro
- Prev by Date: RE: VS 2008 Web Projects will not debug - filename...syntax is inc
- Next by Date: RE: VS 2008 Web Projects will not debug - filename...syntax is inc
- Previous by thread: Attach to Process (not working)
- Next by thread: RE: RaisError in Database Pro
- Index(es):