DSXchange

Why doesn't DS just pass the text to the database, and let the database decide if it's valid syntax or not via whatever return code is passed back from the database? It's frustrating when code that works fine in the native database client fails in DS. I know, but you need to understand you're compa...

I think that what is happening is DS runs the stages simultaneously, opening the connections to the database for all three scenarios above. No, it doesn't, and you should see that when the job runs. Meaning, you should see all rows go into the first ODBC stage and the input side of it close ('finis...

And you don't need to get the count for the loop itself, it will figure that out on its own from the delimited list you send it.

Some projects? Not all minus your problem child? How many are showing / missing?

A Sequence job could use the UserVariables stage in conjunction with the Start/End Loop stages to pull this information out of the file and then iterate through the results. You could also build a Server job to read the file and then leverage the UtilityRunJob() function in the transformer to run an...

Maybe so, but this is a discussion in the Server Edition forum on how to do this in a Server job, not a Parallel job.

When you do a "dsjob -lprojects" what does it show - anything? All of them with the exception of "myproject" or something else? Anything special or different about this one?

Show us the XPath Expressions you are using.

You don't need to store a value from every row into a stage variable, you can keep a value there and only update it when appropriate. Simply set the value to itself to leave it unchanged: svValue: If X Then Y Else svValue Another common 'trick' is to load something into a cached hashed file with a '...

Thanks for posting that, I'm sure it will. Seems you were taking point on this one.

Split it up so that a part without parameters is in the Command box and the rest (the bit with parameters) is in the Parameter box. All the stage does is stick the two pieces together and then run it. The only 'trick' to know is when the very first bit (typically a path to a script) is a parameter, ...

I used that... briefly, back in the day and uninstalled it shortly thereafter. All I remember as to the why is the pretty consistent way to would lock my machine up.

Hmmm... do you really need a q-pointer? Couldn't you somehow 'hard code' the account name of the hashed file in the routine? Much like specifying a specific account in the stage rather than leaving it blank.

:shock: Sarcasm? I was dead serious about never having seen syntax like that and would love to be able to try it on my own to see the behaviour first hand (something I would always do in the past) but being out of work at the moment puts a little damper on that. Didn't say anything to the effect tha...