DSXchange

ShaneMuir wrote: You could have also used something like
Right('00000':AspCodeCountSVar,5)

You could also try writing a parallel routine to do this - nice opportunity to learn C++!

The fields must be marked as Nullable on the output of the previous stage to the Join - it is not sufficient to set a join output field to Nullable if the input does not allow Nulls.

Just to be nosey, but... Is there a field related to your varchar that contains a value for the number of decimal places required? It's just that I've seen this kind of presumption before - 'always two decimal places, must divide by a hundred', when in fact there's a numeric column telling you how m...

For completeness, the nullability of the 'dummy' field affects the value it is set to after the join. If NULL is allowed, then the unmatched 'dummy' field will be set to NULL. If NULL is not allowed then the unmatched field will be 0. Let's hope Ray didn't hurt himself when dismounting from his high...

Combining schema files and Runtime Column Propogation (RCP) could solve your issue.

Slight modification, after trying it... Seems the external filter stage doesn't want to increase the number of output columns, therefore you'll need to have one output col big enough to hold max data e.g. '1234567890 12' i.e. varchar(13). Then use a column import stage to split this single col into ...

Then in that case you may need to consider creating many records for each combination, presumably between 2 and 9 records per input record. Only keep the keys plus the new 'combination field', and join back to the rest of the data after you've joined to get your records to process. If I presume data...

As Craig suggests, I have used 'List all files and tables used by jobs in a dsx file' tool (!!) to good effect.

Is Oracle.Col1 always going to match against characters 2 and 3 of dataset.col1, as your example suggests?? If this is the case, then use a transformer to create a new column based on characters 2 and 3, and perform an inner join between this new column and Oracle.Col1. If the above is not the case,...

Try enclosing $APT_CONFIG_FILE in single quotes to stop the $ being expanded.

You could enclose in single quotes all of your param names so you wouldn't have to make a distinction between env vars and other params.

You can also use the following stages as source, transform or target:

Source: External Source
Transform: External Filter
Target: External Target

You poor naive person!

Get rid of the transformer... any advance?

As an alternative to paying for the membership, you could always try reading the manual

Parallel Job Developer's Guide, Look Up stage, details on Lookup Stage Conditions dialog.

I thought 'dscc' was a client tool for compiling jobs on the remote server? The params needed include server name, user name and password.