DSXchange

Already wrote up something on that subject.

So is your source decimal(13,9) or decimal(13,2)? While you can 'convert' one to the other (13,2 to 9,2), you're going to get that 'limitation' warning when going from a larger field to a smaller one since technically one may not fit into the other. If you are certain the values in the source will a...

How much data are we talking about? How long did you wait before you declared that it was hung?

ps. And there was no year zero, so your ELSE is invalid.

Exactly what I meant by "it also understands key fields so it know which go in the where clause and which don't"... Ray was more explicit (rigorous) in his explanation. Basically two separate sets of ordinal positions.

If nothing here has helped, suggest you start your own post and give us the details of your problem.

An Execute Command stage can read the sequential file via cat and then trigger expressions can check the value and branch accordingly. Alternately, use a Nested Condition stage to perform the check and branching after reading in the file.

They are positional bind parameters rather than explicitly numbered. So generally the first ? gets the first field, etc. However, it also understands key fields so it know which go in the where clause and which don't.

So why is this marked as Resolved?

(Note: I just "unresolved" it! - Andy)

(Heck, I could have done that... was gonna wait for a reply. )

Is this question related to IA / ProfileStage at all?

(Relocated to General - Andy)

Or...

If that reply is directed my way, I wasn't suggesting string math (although I did mention it earlier) but rather simply strings. Seeing as how both the source and target are flat files there's no reason to be treating them as anything other than Varchar fields in my book.

You can't check in the Administrator, that's just the project-wide default. You need to check the individual jobs via the Director as the default could have been overridden there.

Still say they should just be handled as strings.

Typically you see that message on a fixed-width file, is that what you have? Short answer (which the search should have turned up) is your metadata doesn't match with the actual data in the file, specifically it is expecting all of your records to be 208 bytes in length and it found one that ended a...