DSXchange

And the complaint would be?

Nothing inherent to the Sequential File stage. Off the top of my head, you may be able to leverage the Filter option with perhaps 'tr' or some other command to translate your 'multiple character delimiter' into a single character. Or go old school and bring in the record as one long string and then ...

Suggest you try an 'Exact' search for a unique portion of the error, like check that 'gdb' and 'sed' are installed. Urgent usually means solving your own problem as most have been seen before.

Out of curiousity, have you been through the XMLPACK_20_Designer.pdf document? It goes over using the XML Output stage (and the others) in decent detail.

balajisr wrote:This is the job template provided to us.

Whomever provided this to you as a job template should be severly thrashed across the bum.

ArndW wrote:I am somewhat confused by these continued posts on this subject.

Only somewhat?

You need to delete your partial post on this same subject before someone replies to it. Once there is a reply, you can't.

Welcome! Keeping in mind the fact that these 'table details' are purposefully not published, you can find alot of information regarding them posted to these forums. Searching on the individual table names would be one way to start. You'll soon see who the Rock Stars* are. Oh, and you would use LIST ...

yes this is the template we should follow Huh? Do you mean you should have made it two jobs? Are going to? Something else? I, for one, will no longer comment on the design as posted until a screenshot of the actual job canvas is made available. The ASCII art just isn't cutting the mustard, at least...

No, 'fraid I don't. Perhaps someone else would like to take a shot at this now?

For grins, I dug back through my archives and found this. Long before there was a WaitForFile stage, it was a custom routine. From what I recall, it was created by Ascential for a customer that needed the functionality and then eventually turned into an actual Stage. Keep in mind this is circa 1999 ...

Don't you already have a thread on this issue?

Sorry, don't know beans about Sybase... and your problem seems specific to that database.

I really don't see an issue with "loosing" 8 seconds... as noted, we're not talking about anything approaching a real time system here. For the record, the WaitForFile stage scales up the number of seconds it waits over time. From a post over on ADN: Roughly: every 2 seconds for the first 2 minutes,...

That is one way, yes. Certainly not the only way.

How about some details... like what database you are dealing with and what the stored procedure is doing, plus anything else relevant you'd care to share.

Yes, I do. Be in the same spot not all that many hours from now.