DSXchange

It will take time but wont crawl. Load only the columns you need into the hashed file.
OR
get a temp table created in the same schema, and pass a join sql to get the values. That will be much faster.

It will Craig. Just tested it out. After stage routine will fire regardless of the row count.

Load the sql table into a hashed file and perform a lookup based on those two keys. This way for each key present in the sequential file, you will get its corresponding record in the sql table.

You can run an after-stage subroutine in which you can check the rowcount or number of rows present in the sequential file and then pass the return value. Makes sense ???

What exactly do you mean. Give us examples.
Depends upon the precision. Divide by 100 for precision of 2, or 1000 for precision of 3 and so on.
Also specify the length and precision in the output sql type.
Regards,

chulett wrote:Right, it's not about the metadata but the actual contents of the field.

O boy. Good luck on that then.
I, once had that problem. But I could tell by looking at the source and target length. But then again, I guess, I was just lucky.

O yea. Not true outside US. But for all our fellow US dsxians, once again, happy thanksgiving. And for our folks outside, bake a turkey anyways

Ray,
when i copy pasted the box in a unix file, it showed up as ^Z in the vi editor before saving. Once saved, it disappeared showing a blank line, and hence my conclusion that it was control Z even at the unix level.

Read in the help for DSGetLinkInfo().

Happy thanksgiving to all fellow dsxians. Go, enjoy, relax and have some turkey
Once again, this site rules, dsxians rule, and wanted to convey my regards to all.

I guess, commit at regular intervals.
Truncate the table instead of delete.
If your data size is large, request your dba to increase the size. Thats not your fault, its just the data at your hand. Sorry to say but sometimes dba's can be a pain.

But, was there a link collector present in version 4 ?

specify the constraint

Are you referring to the transaction log?
You cannot turn that on/off from an ETL tool. That setting is at the database. Any logged acitivity you do (INSERT, UPDATE, DELETE etc), it will be logged in the transaction log.
Why does that conern you anyways?

You have to specify that at the last column. I just tested it. The job runs fine.