SQL node issue

[missspeedy23]

I have an SQL node in a jobstream to update a table:

UPDATE RUN_VERIF_REPORT
   SET RUN_REPORT = 'Y'
      ,REPORT_LAST_RUN_DATE = GETDATE ()

When I run the code in SQL Server Management Studio directly it executes and updates fine. When I run the node on Data Manager it doesn't seem to do anything at all.

Any info/advise greatly appreciated!

[MFGF]

I have an SQL node in a jobstream to update a table:

UPDATE RUN_VERIF_REPORT
   SET RUN_REPORT = 'Y'
      ,REPORT_LAST_RUN_DATE = GETDATE ()

When I run the code in SQL Server Management Studio directly it executes and updates fine. When I run the node on Data Manager it doesn't seem to do anything at all.

Any info/advise greatly appreciated!

Hi,

Do you get an error from the node, or does it complete successfully? What is the "Action on failure" for the node set to be? When you are looking at the SQL tab of the node, what data connection is it set to use? If you look at that connection in the Library, does it point to the database you assume it does?

MF.

[missspeedy23]

Hi,

Do you get an error from the node, or does it complete successfully? What is the "Action on failure" for the node set to be? When you are looking at the SQL tab of the node, what data connection is it set to use? If you look at that connection in the Library, does it point to the database you assume it does?

MF.

Hi, no there are no errors at all on the log so it seems to complete successfully. The action on failure is terminate. It is set to use our database called "Staging" which is correct and yes I've checked the connection itself as I did wonder if that might be the problem but a number of other builds use that connection and update the database fine so it's not that.

[MFGF]

Hi, no there are no errors at all on the log so it seems to complete successfully. The action on failure is terminate. It is set to use our database called "Staging" which is correct and yes I've checked the connection itself as I did wonder if that might be the problem but a number of other builds use that connection and update the database fine so it's not that.

Is the SQL node in a branch of the jobstream that doesn't get executed? You could try inserting a procedure node immediately before the SQL node, and code the expression for the procedure node as

logmsg(concat('About to execute SQL node at ',DateTimeNow()));

Turn on User Logging in the properties of the jobstream and see if the message appears in the jobstream log.

You could also turn on Detail logging in the jobstream, which will tell you what nodes are running too...

Cheers!

MF.