DSXchange

Sure, if what you want is the last record FROM EVERY NODE.

Sure, if what you want is the last record FROM EVERY NODE

Is it case sensitive?

When you say "type" are you referring to Windows type (for example administrator versus non-administrator) or InfoSphere Information Server type (for example which roles have been assigned to you)? Or something else entirely?

Perhaps the excluded sheet names need to be separately quoted? Particularly as each appears to include a space character.

Great! Thanks, Robert.

ani_chutti@yahoo.co.in wrote:There is no choice for multiple job design. All these has to be designed in one single job

Why?

Resist stupid requirements! Or is it an interview question?

... and Information Server metadata importers have (currently, at least) no mechanisms for interacting with tools such as DbVisualizer.

You need to import table definitions from the tables accessed by the query. There is no mechanism for importing from the query itself; it contains no other useful metadata than the column names (and even some of those can be generated "on the fly" using AS keyword). Perhaps you could creat...

The usual approach in this case is to encase the identifiers in double quotes.

No.

ODBC 3.0 (and presumably 3.5) Grammar specifies that identifiers will begin with alphabetic or underscore characters only. Therefore the ODBC driver (correctly) does not have the inbuilt capability to manage metadata that do not conform to this specification.

It appears that someone has been deleting projects.

Welcome aboard.

Does not MS-1252 recognise these Windows special characters?

You can do a range lookup on either the reference input or on the stream input. Examine the examples in the Knowledge Center or in the Parallel Job Developer's Guide.