"Ravi" <ar.ravi@verizon.net> wrote in message
news:ujjpQTGGEHA.1396@TK2MSFTNGP11.phx.gbl...
> In DB2, SQLCODE = 100 and SQLCODE = 0 are the key validations one would
> make after an SQL statement to see if the query was run successfully or
not.
> If the query returned any rows or not. Is there an equivalent syntax in
MS
> SQL ?
>
>

"Ravi" <ar.ravi@verizon.net> wrote in message
news:ujjpQTGGEHA.1396@TK2MSFTNGP11.phx.gbl...
> In DB2, SQLCODE = 100 and SQLCODE = 0 are the key validations one would
> make after an SQL statement to see if the query was run successfully or
> not.
> If the query returned any rows or not. Is there an equivalent syntax in
> MS
> SQL ?
>
>

"Aaron Bertrand [MVP]" <aaron@TRASHaspfaq.com> wrote in message
news:#WLMwVHGEHA.3032@TK2MSFTNGP09.phx.gbl...
> You can check @@error for errors, and @@rowcount for number of rows
affected
> by the statement. If they aren't what you expect, act accordingly.
>
> Note that any statement resets these values, so you'll want to capture
them
> to local variables immediately, and at the same time if you want both.
e.g.
>
> DECLARE @err INT, @rc INT
> -- statement here that may cause error
> SELECT @err = @@ERROR, @rc = @@ROWCOUNT
>
> --
> Aaron Bertrand
> SQL Server MVP
> http://www.aspfaq.com/
>
>
>
>
> "Ravi" <ar.ravi@verizon.net> wrote in message
> news:ujjpQTGGEHA.1396@TK2MSFTNGP11.phx.gbl...
> > In DB2, SQLCODE = 100 and SQLCODE = 0 are the key validations one
would
> > make after an SQL statement to see if the query was run successfully or
> > not.
> > If the query returned any rows or not. Is there an equivalent syntax in
> > MS
> > SQL ?
> >
> >
>
>

"Ravi" <ar.ravi@verizon.net> wrote in message
news:uTK$ulKGEHA.628@TK2MSFTNGP10.phx.gbl...
> Thank you. I cannot say the select did not find any since @@error was 0
> even when the select did not find any row for the criteria requested. I
> will try with @@rowcount approach. Probably, that should have 0 to tell
> me there were none selected.
>
> - Ravi