DSXchange

For the sake of everyone here trying to help, please go back and edit your post. Take your code, format it nicely and then paste it back wrapped in 'Code' tags so the forum preserves the formatting.

Thanks.

One million keys, max.

The 'custom folders' need to be in the project you are versioning. Since I'm sure that's not the case, create a link from where they really are to something of the same name under the project - then you will be able to version them.

Yuck, whatever for. Still, I think you'll find using a Timestamp type and your current format will work - even in ODBC.

Make sure the Transaction Size is zero in the OCI stage and the job aborts if there are any problems with the XML generation. However, that was a pretty 'off the cuff' comment and it may not work properly all the time in that configuration now that I think about it more. You'd need to link them toge...

Ah... but you could. Drop a second Transformer in there and hook the OCI stage to that one instead. Add a dummy stage variable, the macro in the derivation and a constraint on the output link of @OUTROWNUM=1 and you'll always get one row down it, even if the 'main' job processes zero rows.

Sure... so? Not like you'd run like that over the course of a normal day. And I only do that when I've got a specific filter enabled, otherwise you are asking for a world of hurt... especially pre 7.5 - at least you can bump the refresh interval up to a reasonable level or completely disable it now.

I beg to differ - in my experience it only 'refreshes' the jobs in your current category.

Should be there under the derivation editor ellipsis (...) as a Function in the Conversion category. At least it was there in 7.0.1.

I would do the same - there's absolutely no reason to force a wait until the end of the job to record the time the job started.

Actually, if you are using an OCI stage and a datatype of Timestamp - you've already got it in the proper format.

Can you not create a dataset keyed by city with the country it is in as the data element? Then you can look it up on the way in and use it if the original value is null. Only problem with that would be when the same city name is in multiple countries...

512MB is barely enough to run XP. Is there a workstation there with more? I have 2GB but even 1GB would help tremendously.

Trim(YourStringField,'"',"A") A double-quote inside two single quotes.

I've imported from 200 or 300MB exports without anything timing out. Depending on the speed of your machine and how much RAM you have, it can take quite some time, however. An xml export will take even longer as it is first converted to a dsx 'under the covers' and then imported. Patience is the key...