DSXchange

Yes it is expected. When converting decimal to string DataStage adds a decimal placeholder and sufficient leading and trailing nonsignificant zeroes to make it clear what the precision and scale settings are.

What do you get if you don't apply the Convert() function, since you assert that there are no "junk" characters present in the data?

Perhaps a better term would be non-alphanumeric.

Or you could use a loop in a Transformer stage, WHILE Index(InLink.TheField, '"', 1) > 0
Within the loop replace the double quote using substring techniques.
Perhaps make use of the LastRecordInGroup() function to constrain the output.

Check the date (year) that that Redbook was publlished.

and describe the data type as VarChar(36). You may also need a function such as RAWTOHEX() in the SQL.

The istool command also has options for creating a package.

Take a look at what's specified in the fr_FR locale. You may need to create a custom locale definition.

Otherwise read the field as VarChar and use Convert() function to change the delimiter characters.

You could always perform an update immediately after the initial load.

That's not how ODBC works. You WILL need a separate connection to each database, unless you create links from one database (to which you connect) to the other four within SQL Server.

Try saving the table definition from a job in which the metadata work successfully then right clicking within the columns grid of the saved table definition to produce a schema file.

As a general rule anything with an all upper-case name is an environment variable. Project environment variables are maintained using the Administrator client. You can add environment variables to those supplied "out of the box".

You didn't ask another question. I assumed that

TonyInFrance wrote:I guess I need to define an NLS locale just to signify a thousands' separator.

was a statement of intent.

Bonne chance!

Click the "job report" tool to produce a report of the job design, and copy your stage variable information from the report thus produced.

No publicly-available sources, but I do participate in the early-release program and have some knowledge of future plans from that. Of course, anything specific is covered by non-disclosure agreement.

Minimum value for signed decimal[1,0] is -9.0.
Minimum value for unsigned decimal[1,0] is 0.0.
Minimum value for signed decimal[5,2] is -999.99.
Minimum value for unsigned decimal[5,2] is 0.0 (which is the same as 000.00).