DSXchange

Because of the nature of your parameter, you need to write a procedure and build dynamic SQL that the proc executes. It's not about local variables, it's about the nature of the binding you are doing.

I don't believe there is a way to control the XML Output's filename based on input data, at least not that I found in the versions I worked with. You give it a base name and you can control the split to a new filename with the Trigger Column, but you are stuck with the sequential numbering it does. ...

devnhi wrote:It is not taking OVERWRITING as the filename though ..Anything wrong with my syntax?

I assumed you were creating the VOC record with SETFILE, hence the OVERWRITING comment. No clue why you'd be using ED.

Sort the data by the grouping columns and then assert in the Aggregator that your input is sorted.

SQUAWK?

You have to write a procedure in the db and then call the procedure in the Stored Procedure stage, it won't run "procedure code" directly.

I would argue against a "current date" file check but would implement an "unprocessed" file check. Move/archive the files elsewhere after processing so that anything found in that directory needs to be loaded, this allows you to catch up if need be.

Something has to run to check the files, so yes a Sequence job would be appropriate and it could trigger the processing job only if a file is found.

Create a new (temporary) project and copy from there?

Again, start by posting in the correct forum - the FAQ Discussion forum is not it.

No clue. Contact your official support provider.

Start by posting in the correct forum.

Add the keyword OVERWRITTING to the command.

mouthou wrote:And also surprisingly it generates the same duplicate random numbers for the consequtive runs.

Not sure why, that's the way all "random" number generators work given the same seed value.

Show us exactly what you tried in the External Source stage.