DSXchange

I would imagine you could find the buffer size limit by asking your Teradata DBA.

So, to get the date from a particular pair within the record: Field(Field(record,",",pair_number),"|",2) The inner Field() call returns the pair--such as BBB|5/24/11--then the outer Field() call returns the date from that pair--5/24/11. Exactly what I meant when I said "Inl...

Inline Field() functions, perhaps. First use "," as the delimiter and then take the second "|" delimited field from the result.

Done... thanks! :D

Your official support provider? Otherwise it seems to me that you'd need to wait for someone with both 8.7, SQL Server and extended timestamps experience to come along. I've got none of that, for example.

I can't explain the behaviour off the top of my head... what flavor of UNIX is this? What happens if you change your command to this:

I'm going to suggest something that some might consider heresy - remove the IPC stages, disable row buffering. I found them to cause way more problems than they (allegedly) solve and never used them. As noted by Ernie and other folks way more smarter than me, they're no magic bullet.

Sounded like your repositories (there are two) were not in sync and may still not be... that or there is some element of corruption there. Best to get your official support provider involved for help with that.

Yes, it is stored separately from the logs. If the job instance is no longer showing in the Director, I'd imagine you could still restart it from the command line.

In what release was support for null stage variables added? They didn't up until fairly recently, from what I recall.

I already did. Convert() won't care how "dynamic" it is... assuming I understand what you mean by that.

Yes, if that's really what you want.

What's not working about it? Why not just Convert() the commas to carriage returns?

Your Field() function call is syntactically correct. Is your target a sequential file? If so, then you need to use CHAR(10) as the record delimiter. If not, you need to give us a better explanation of exactly what it is you are trying to accomplish, i.e. what your requirement is.

Yummm... ORCAKE.