DSXchange

It is possible, and it will work for 30 days before the Data Direct company will want money to keep the ODBC driver working. Search the forum for "BCI". Or you could create a shell script, and invoke that via DSExecute(). But the approach using a separate job is cleanest and easiest to maintain; aft...

Read my previous post again, then follow the advice therein. The query may be entered using the Administrator client's command window. The single character inside the single quotes inside the double quotes is an upper case letter O. Is it only in the Palette that you are getting "no stage types", or...

Certainly it will perform like one in terms of fuel (CPU, memory) consumption!

"Not configured" typically means that there is no entry in the uvodbc.config file in the project directory on the server for that particular DSN.

Cleanup is required at the Teradata end. Discuss with your DBA.

If it was impossible before why should it be possible now?

The bulk loader (sqlldr) and triggers are inimical.

If you must have the trigger then you must perform all inserts using SQL.

If you must have the bulk loader then you must - temporarily at least - drop the trigger.

Telenet wrote:I've allready got it solved. I've removed the partitioning and sorting from the input of the filter stage and preceded it with a sort stage doing exactly the same thing.

Well done. Why does this work? Why did you think to try it?

What you seek to do could be termed "cascaded lookups". To use the GUI you need to use two Transformer stages, passing the region data from one to the next. You can do it in one Transformer stage, but will need to type the region.regionkey reference into the second lookup's key expression; the GUI o...

Every plug-in stage belongs to the class CCustomStage in server jobs. You need to ascertain what stage type you think it is, then to determine whether that stage type exists in the Repostiory database, bypassing the index. LIST DS_STAGETYPES ID.SUP NO.INDEX BREAK.ON "'O'" CATEGORY FMT &quo...

Thanks for posting the resolution. Hopefully it will help someone else in the future. Meanwhile, can you please mark this post as resolved? (Only the initiator may do so.)

Why not? This is precisely one of the tasks that the Data Set Management utility is intended to perform. Perhaps you do not know how to use it properly? Did you nominate the Data Set control file in the utility? Was there an error message when attempting to delete the Data Set? If so, what was it?

That's even more confusing! Please supply examples WITH NUMBERS as requested. Does there exists a written specification for this logic? That is, some form of target-from-source mapping document? Your terminology is also confusing. At one moment you are referring to a Transformer - at the next moment...

Not in the same job. You would need to obtain the table name in an upstream job and store it somewhere. In the downstream job make the table name in the target stage a job parameter reference. In the job sequence that runs both of these jobs, read the table name from its stored location to load a va...

No. The "ODBC driver licence issue" does not occur on Windows platforms, as far as I am aware (unless, of course, you choose to use the Data Direct drivers).

If it were the licensing issue, the routine would not work under either scenario.

Keep detecting!