DSXchange

Not really seeing a problem here as it looks like you just choose the first non-empty value of the three and output that. That's just IF-THEN-ELSE. Or am I missing something?

Short answer? Yes. Use whichever has the most frequent action first. If mostly inserts chose "Insert then Update". Etc. Of course there's more to it than that but... yes.

Make sure you run your job on a single node, that should take any 'randomness' out of the picture.

Okay... but isn't that limited to canned reports based on metrics of job stats that the tool automatically captures for this very purpose? Or is it more... open... than this and something anything can be published to?

Kim is talking about building a formatted HTML page rather than an Excel spreadsheet by creating all of the needed "tags" manually, which could then be opened by a browser... and technically Excel as well. If that's not already in your wheelhouse (building web pages and the like so you are...

There's no need to send Private Messages, everything gets looked at and can be answered by anyone and everyone. In the forums.

That's not really what ETL tools are meant / designed to do. A more typical solution would be for the ETL 'report' to be data loaded into a table and then something else, a BI tool for example, to do the dashboard Make Pretty part.

Involve support.

I doubt you can, it probably just uses the default Windows font which would mean changing it everywhere. But perfectly happy to be proven wrong!

Other than what I already posted? No.

http://www-01.ibm.com/support/docview.w ... wg21962771

About all it seems to me you can tell from the message is that it is a 1 character string and it wanted to put 2 characters in it.

I'd also be curious if this used to work and no longer does or if this is the first time you've used the connector and thus has yet to work properly.

I'm a little lost here. You have a stored procedure that somehow 'generates' three output datasets at once? Or is this 'one after the other'? And then exactly what do you need to do with this? Other than read in one go and do some manipulation, I mean. You have three different targets that you'll ne...

As noted by Ray, rather than using a "current timestamp" that you either pass in or generate, why not use the system variables or macros that hold the Job Start Timestamp which would be available anywhere in the job and are a constant since they are set in stone when the job actually start...

That's what I suspected but had no way to verify except through others - the hard break between the exception handling and the body of the sequence is what leaves any variables not in the exception "timeline" out of reach. The 'problem' with adding another there just for the CURRTIME is it...