sunilsoni30

 Profile Answers by sunilsoni30 

• Jun 21st, 2008

 

error<> o

seemu123

 Profile Answers by seemu123 Questions by seemu123

• Jul 1st, 2008

 

In SQL Server 2000
 We can check by @@Error<>0 i.e. error.
ex:
     IF @@Error<>0
          BEGIN

             ROLLBACK TRANSACTIOn

             RETURN

          END

     ELSE

          BEGIN

             COMMIT TRANSACTION

             RETURN

          END

Note: You need to check @@Error at every DML statement and since it is Global Variable, So it reset every time.

In SQL Server 2005
We can check by using try catch block
ex:

BEGIN TRY

BEGIN TRANSACTION
/*statement*/

COMMIT TRANSACTION

END TRY

BEGIN CATCH

IF @@TRANCOUNT>0

ROLLBACK TRAN

END CATCH

Note: You can check the following functions in catch block
a)ERROR_NUMBER() returns no of the error
b)ERROR_SEVERITY() returns severity of the error
c)ERROR_STATE() returns error state no
d)ERROR_PROCEDURE() returns name of stored procedure
e)ERROR_LINE() returns line no.
f)ERROR_Message() returns the complete text of the message

suaveshiva

 Profile Answers by suaveshiva 

• Jul 17th, 2008

 

Abt Clustered indexes:
V can hav only one clustered index in a table, by default primary key is termed as  clustered index.
V can have 249 non-clustered indexes in a table.

yemshivakumar

 Profile Answers by yemshivakumar 

• Sep 2nd, 2008

 

We can use @@ERROR keyword for handling errors.  RAISEERROR also we can use.

Tinkerbell

 Profile Answers by Tinkerbell 

• Feb 21st, 2009

 

You can have only one clustered index on a table and a maximum of 249 non clustered indexes.

kirangiet

 Profile Answers by kirangiet 

• Aug 16th, 2010

 

1) CLR is integrated in SQL Server 2005. Hence we can use below code for Exception Handling.

BEGIN TRY       

SELECT * FROM Employees; 

END TRY 

BEGIN CATCH     

SELECT          

ERROR_NUMBER() AS ErrorNumber,

ERROR_MESSAGE() AS ErrorMessage; 

END CATCH

2) With SQL Server 2008 we can have 1 Clustered Index and 999 Non Clustered
indexes (Not 249)

3) As far as my knowledge is concern disconnected mode is a ADO.NET concept
and has to do nothing with SQL Server. This can be achieved using DataAdapter.
Hence when we require to interact with DB we will connect and once we are done
with it connection will be disconnected. In order to work with connected mode
use SQLCommand.

Pradeep Kumar Sharma

• Dec 25th, 2011

 

Begin Try

--
--
End Try
Begin Catch

Declare @errMsg varchar(1000),@errSev int
select @errMsg=error_message(),@errSev=error_severity()
RaisError(@errMsg,@errSev,1)

End Catch