Interviews World
 .Net (166)
 
  .Net Framework(43)
  .Net Memory Management(2)
  .Net Web Service(6)
  .Net Remoting(30)
  .Net Security(2)
  .Net Threading(8)
  .Net Architecture(2)
  Basic C#(33)
  VB.Net(2)
  .Net Window Service(3)
  .Net Window Forms(14)
  Advanced C#(25)
  Visual Studio 2003(2)
  Visual Studio 2005(2)
  Visual Studio 2008(2)
  Visual Studio 2010(2)
 
 ASP.Net (49)
 
  ASP.NET General(7)
  ASP.NET Caching(9)
  ASP.NET Ajax(13)
  ASP.NET Session(7)
  ASP.NET Localisation(2)
  ASP.NET 1.1(2)
  ASP.NET 2.0(2)
  ASP.NET 3.5(11)
  ASP.NET 4.0(2)
 
 Database (88)
 
  SQL Server 2000(20)
  SQL Server 2005(24)
  SQL Server 2008(42)
 
 ADO.Net (7)
 
  General ADO.NET(7)
 
 Object Oriented (27)
 
  Basic Object Oriented(19)
  Advanced Object Oriented(8)
 
 XML (24)
 
  Basic XML(24)
 
 MS Dynamics (1)
 
  MS Dynamics GP 9(2)
  MS Dynamics GP 10(1)
  MS Dynamics Soloman(2)
  MS Dynamics CRM 3.0(2)
  MS Dynamics CRM 4.0(2)
  MS Dynamics CRM 5.0(2)
 
 Sharepoint (65)
 
  Basic SharePoint(35)
  SharePoint Server 2003(4)
  SharePoint Server 2007(25)
  SharePoint Server 2010(2)
 
 HR (2)
 
  Basic HR(2)
 
 Java (1)
 
  Basic Java(1)
 
 PHP (2)
 
  Basic PHP(2)
 
 Testing (15)
 
  Automation Testing(15)
 
 
  Welcome to Interviews World
 

$5 .COM Black Friday Sale!


Question : What is the error handling in stored procedures of SQL Server 2008?

Answer :

In previous versions of SQL Server you would handle exceptions by checking the @@error global variable immediately after an INSERT, UPDATE or DELETE, and then perform some corrective action if @@error did not equal zero.

SQL Server 2005 provides structured exception handing through TRY CATCH block as other programming language like JAVA, C# etc.


BEGIN TRY
    RAISERROR ('Yaa, I ma the problem', 16,1)
END TRY
BEGIN CATCH 
SELECT ERROR_NUMBER() as ERROR_NUMBER,  
ERROR_SEVERITY() as ERROR_SEVERITY,  
ERROR_STATE() as ERROR_STATE,  
ERROR_MESSAGE() as ERROR_MESSAGE
END CATCH
 

  • ERROR_NUMBER() returns the number of the error.
  • ERROR_SEVERITY() returns the severity.
  • ERROR_STATE() returns the error state number.
  • ERROR_PROCEDURE() returns the name of the stored procedure or trigger where the error occurred.
  • ERROR_LINE() returns the line number inside the routine that caused the error.
  • ERROR_MESSAGE() returns the complete text of the error message. The text includes the values supplied for any substitutable parameters, such as lengths, object names or times.
 
 
  Website Highlights
 




















 
 
 
  Newsleter
 
Enter your Email:
Newsletter