DSXchange

By the time you are ready for very large keys to be generated you will have version 8 or later, in which the Surrogate Key Generator stage is equipped to generate uint64 values.

That's 18446744073709551616 distinct key values. Enough for you?

You might even begin by asking your SAP BW experts about the BW Transfer Structure.

No worries, cobber.

Then I guess the problem is "or accessed by others" - did someone else have the xyz table defintiion open while you were importing into MetaStage, or is the xyz table definition used in other jobs that you were not importing? In Manager perform a Usage Analysis on the xyz table definition.

Welcome aboard. :D

There is no Metabroker specifically for Excel. However, you could import the table definition via ODBC (provided the Excel worksheet is in table format with column headings) using the ODBC metabroker.

Unfortunately we can not offer you a tax deduction. On the other hand, a smart accountant may be able to justify "self education expenses".

OK, your site has not licensed server jobs. They have a server licence; they've just decided not to use it. So your next best approach is to use a parallel job that includes a BASIC Transformer stage, and invoke the routine from that. Make sure that the BASIC Transformer stage - indeed the whole job...

Have you tried the "whole SQL statement as job parameter" approach yet? There's got to be some reason folks use it.

May we know what the bug was, what the patch was/does, and what the ECASE number is? That will help anyone in future who encounters the same bug. Hopefully.

Please post server questions in the server forum.

Use the NullToEmpty Transform

Welcome aboard! :D

This is an executable job, not a job sequence. Recompiling that particular job may well re-create the job parameter instances record in that job's configuration file. Please try it and let us know the outcome.

You CAN code it. But you need to think about what algorithm you will use. For example, what argument(s) will the routine expect to be passed to it (perhaps year and month only, perhaps the result of the MONTH.LAST Transform)?

It IS inner join You just need to do the substring piece in an upstream stage.

You're correct, the ODBC stage does not like a job parameter reference as table name. However, it will accept (as user-defined SQL) an entire SQL statement that is a job parameter! That's how most folks work around this restriction. You can build the SQL in the parent job sequence when the table nam...

You don't write code in a sequencer, or even in a job sequence. You need to create a server routine and invoke it through a Routine activity from a job sequence.

Can you please outline the algorithm that you want translated into code?