How to get the return code of sp_executesql?

Question

0.00/5 (No votes)

See more:

MSDN says sp_executesql returns code values 0 on success and any other non-zero value on failure. How do I catch it in a variable? A simple example please.

Also, can it be gotten in MSSQL 2005 just the way I described?

Regards!

Posted 1-Aug-15 6:59am

priyamtheone

Add a Solution

Comments

RedDk 1-Aug-15 20:06pm

sp_executesql ... used here:

http://www.codeproject.com/Articles/36584/How-To-Store-Any-File-into-SQL-Database

Can't for the life of me understand what you mean by "catch it in a variable". But you refer to return code 0, so you you must know something, right?

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

DamithSL · Accepted Answer · 2015-08-01T07:19:00

Solution 1

SQL

declare @ret as integer;
exec @ret = sp_executesql .......;

Posted 1-Aug-15 7:19am

DamithSL

Comments

Wendelius 1-Aug-15 14:04pm

Short and simple, 5.

DamithSL 1-Aug-15 14:18pm

Thank you, Mika

priyamtheone 2-Aug-15 11:39am

Oh, it's as simple as that! Wrote the same code last day but didn't work, and I had to post this silly question over here. Later on found out a syntax error in the query statement that was causing the headache. Anyways, it's never bad to review simple things in times. Thanks DamithSL for re-teaching the nursery lesson. :-)

DamithSL 2-Aug-15 11:46am

don't worry we all in same boat ;)