Skip to main content
Question

SQLExecutor + Stored Procedure in MSSQL: Executed or not?

  • November 15, 2012
  • 2 replies
  • 67 views

sigtill
Supporter
Forum|alt.badge.img+25
When using the SQLExecutor with a Normal SQL like:

 

SELECT *

 

FROM mytable

 

WHERE id LIKE 11111

 

 

It will return an attribute "_matched_records" with the number of records matched in from TRIGGER port.

 

 

However when using an EXEC-statement this does not seem to happen. Like this:

 

EXEC @return_value = [dbo].[myStoredProcedure] @ID = N'@Value(IID)',

 

@myTableValue = N'@Value(myValue)',

 

 

 

So after doing this it is not possible to figure out if the EXEC have actually run and inserted the needed attribute - or if there is an error performing this request. Anyone with a good workaround OTHER than doing another SQLExecutor to try to read back the data and try to compare the features? (Many features = alot of time reading and writing)
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

2 replies

sigtill
Supporter
Forum|alt.badge.img+25
  • Author
  • Supporter
  • November 15, 2012
A thank you goes to Ken Bragg that helped solve this issue. The solution was to add SET NOCOUNT ON; on the StoredProcedure.

fmelizard
Safer
Forum|alt.badge.img+22
  • Safer
  • November 15, 2012
Although I have to admit - I stumbles upon that while doing a really complicated work-around. Luck!