DSXchange

First off, this is incorrect: 2) Procedure Type: Transform That would mean it is in the middle of a job with input and output links. Yours should be set to 'Target'. Also note that there absolutely needs to be "metadata" there, meaning your row generator should be sending the single column...

All that is happening here is the job that the Sequence is running, the "does nothing but create 10 rows" job which you said "works fine", is aborting. The sequence job's log shows it being reset and run, meaning it had aborted before and needed to be reset before it could be run...

Help us understand your situation. Is this something that was working and has stopped working? Or from your comments is this part of an installation attempt, i.e. a new installation and you are trying to get them to start for the first time?

thiagobertho wrote:I have to use a routine?

Yes, and hopefully this conversation on the topic helps.

Developer9 wrote:Admin Team Prefers us to do at job level.

Yeah... no.

So... as a total SWAG on my part... is there a way to include the extended "Unicode" property in the schema file?

Okay, fair enough. The only reason I asked was because you said you were "facing issue": I am facing issue while parameterizing the connection details It would have been better to simply ask for help, for guidance on how to parameterize them. And Ray has covered that, let us know if you ha...

You did catch the fact that the "bug" they are going to fix is removing the RCP button/checkbox as it is not valid with SF, yes? Not making it work somehow. Just double-checking. Or perhaps you can check to see if perhaps it should / will be supported now...

What kind of issues, exactly?

And sorry, but just to be pedantic it is the stored procedure stage.

eostic wrote: ...where karge is hundreds of stagrs?

Guess I need to get caught up on the latest techno-babble.

Why not just do this "in job" rather than burying it in the After SQL?

Thanks Ray, I was really hoping someone else would pop in here and help out. Ray for one is always championing using the right tool for the right job and that means Server jobs when there's really no need for all the overhead of a Parallel one to do something pretty straight-forward, like as a timel...

Okay. Just to level set, I assume this job to produce those files is a Parallel job. If so, are you at one of those shops where Server jobs are forbidden? You could easily use one to read the table and build a 'ready to go' delimited string and actually use the true USERSTATUS area to pass that alon...

Okay, fair enough... what exactly is the job in the Job Activity stage doing to generate the email address list? Guessing it gets them from a table somewhere and then writes a delimited list out to a file? Clarify that for us please and we'll see if we can improve this part of the process for you.

Okay, in that context... There's no reason to go through all of those steps for "dynamic" parameters, be it in a sequence or otherwise. That is a very old school approach, something we had no choice but to do Back In The Day as there was no other mechanism. Well, other than USERSTATUS whic...