DSXchange

Joins have specific meaning to relational database processing. There are types: inner, outer, left, right, full, etc. Within some of those types there's a concept of a driving (driver) table, whereby that driver table ultimately decides how many target rows will end up in the result set (minus any f...

Sorry, but the only option that I know works is to have a view created on the production server that aliases the column under a new name.

What don't you like about remsh, rlogin, rsh, etc?

Don't write to files on a full file system.

Don't write rows to a file with a NULL primary key value.

Don't write rows to a corrupted file.

You're getting closer. :D

I'm saying DataStage is not exercising your query. The viewing of reference lookup data is meant to repeatedly fetch a lookup row during processing. By pressing the "View Data" button, DataStage is NOT generating a list of values to repeatedly feed the query so that rows return. How would it know wh...

Is your constraint in this syntax?

This is a reference lookup, right? When pressing view data, don't you think this query requires the "= :1 " part of the WHERE clause to be given a value, so that it can return a row? But you're expecting a bunch of rows, right? So which rows? Your brain should be tingling right about now. The answer...

How about use DS API's to extract link metrics for row counts and write them to a text file. Then use a standard job to load that data into a database table. Simple SQL in your target database can compare row counts.

Don't bother with the surrogate key generator stuff, the file line number is sufficient and easy. If you already had the source data separated into discrete files, your only issue is to keep each file in original order, and keep rows separate. Since DS Server jobs read files in order and write them ...

Kenneth, Five containers suggests to me 5 passes through the data. This doesn't seem very efficient. For sake of discussion, if efficiency did not matter, then why not just grep the data for the specific record-type in each of 5 sequential stages? Where's the benefit of using containers? Can you el...

Sure, as long as the values are YYYY-MM-DD HH24:MI:SS a comparison will work because this string format lexicographically compares left-to-right in ascending order.

Do other rows work, or is every row failing? Did you press the GetSQLInfo button on the ODBC stage properties tab? Can you take this row of data and run the DELETE statement yourself to see if the query works for this data? You know: DELETE FROM AITTRNEE WHERE ERROR_CODE = 0 AND TRAN_ID <= 183619 Wh...

You do realize that the ODBC drivers that ship with DS are only licensed thru the ETL tools, and any direct usage via programming, which includes your DS BASIC programs, is not covered under the licensing agreement? This means you will get 30-day usage warning messages on every query executed, and t...