Output/Return
-
Any specific guidelines when we should go for return/output wrt SQL Server stored procedures. If i have only one output to return? Thanks, Amit
-
Any specific guidelines when we should go for return/output wrt SQL Server stored procedures. If i have only one output to return? Thanks, Amit
Does your app need to work with the returned value?
"Any sort of work in VB6 is bound to provide several WTF moments." - Christian Graus
-
Does your app need to work with the returned value?
"Any sort of work in VB6 is bound to provide several WTF moments." - Christian Graus
Means?
-
Means?
Ummm, does your app do anything with the returned value? E.g. report the row count, put the returned values in a datagrid, etc?
"Any sort of work in VB6 is bound to provide several WTF moments." - Christian Graus
-
Any specific guidelines when we should go for return/output wrt SQL Server stored procedures. If i have only one output to return? Thanks, Amit
I tend to reserve the return value for succeeded/failed notifications, where I haven't used
RAISERROR(which throws aSqlExceptionin .NET client code). The return value can only be an integer, while output parameters can be any type. I rarely use output parameters unless it's an out-of-band value, not associated with the other data in a result set, and I don't want to return an extra result set just containing that data.Stability. What an interesting concept. -- Chris Maunder