Well if you are using SQL 2000 then in that case I believe the @@ERROR can be of...

Garadin (10/8/2009)

---

Just because your query doesn't return any rows, it doesn't mean that the server didn't have to read through a large amount of data to come to the conclusion...

How about this ?

DECLARE @Table_A TABLE( id INT IDENTITY ( 1 , 1 ),data VARCHAR(25) )

DECLARE @Table_B TABLE( id ...

I'm not sure whether you're already doing it or not, but you can use the try...catch block to achieve this. Below is a small sample.

CREATE PROC testerror

AS

BEGIN TRY

SELECT...