dcsimg
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

By submitting your information, you agree that devx.com may send you DevX offers via email, phone and text message, as well as email offers about other products and services that DevX believes may be of interest to you. DevX will process your information in accordance with the Quinstreet Privacy Policy.


Tip of the Day
Language: Enterprise
Expertise: Intermediate
Sep 21, 1999

WEBINAR:

On-Demand

Building the Right Environment to Support AI, Machine Learning and Deep Learning


Test the Execution of a T-SQL statement Using the Value of @@ERROR

When SQL Server completes the execution of a T-SQL statement, @@ERROR is set to the value 0 if the statement is executed successfully. Otherwise SQL Server returns an error number. Remember that @@ERROR returns the number of the error message until another T-SQL statement is executed. Because @@ERROR is cleared and reset on each statement execution, you should check it immediately following the statement being validated. Alternatively, you can save it to a local variable that can be checked later.

Text associated with an @@ERROR error number can be viewed in the sysmessages system table. A typical usage to check for a check constraint violation (error number 547) in an UPDATE statement is shown below:

 
USE MyTable
GO
UPDATE FieldNameID SET id = '100' WHERE id = "100"
IF @@ERROR = 547
print "A check constraint violation or conflict 
occurred in database table"
Jai Bardhan
 
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