DSXchange

Actually it's much better in 8.7. There are two glossaries - the development glossary and the published glossary - if you choose to enable the workflow feature. Straight away you've got better governance. On top of that there are new roles within BG: Editor (who can change things) and Publisher (who...

No.
No.
and No it won't.

Not enough information.

What is the expected output?

Please provide a written specification of the transformation needed in the requirement.

Why is this required? It it, perhaps, an interview question?

You've supplied a two digit year but your date format string specifies a four digit year.

Provided your database server can cope with an SQL statement that long, it should be OK.

You could always create a hybrid approach, such as a sequence with multiple loops each handling a subset of lines from the list of table names.

If you don't do anything to corrupt the state file, such as opening it with a text editor, the state file is also perfectly safe - it does not corrupt itself.

View the data how?

You can't. In this scenario there may be students doing some courses but not others, and courses in which some students but not others are enrolled. Because the sources are different (student-centric and course-centric) you're probably safest to partition on both join keys.

Plan carefully.

Avoid scope creep.

What do you mean by "dataware"?

You can use Sequential File stage for "flat files" - single record structure, ideally no packed decimal data - sourced from mainframe. Prefer Complex Flat File stage for others - multiple record structures, packed decimal data, etc.

But it did it successfully (status = 0), which means that nothing was passed in.

Is VER_ID a parameter of the sequence? Please be aware that parameter names are case sensitive.

Presumably using the correct version of the Update Installer.

The point we've been trying to make is that a sequence job with a loop means that you process one table at a time. A UNION can (theoretically anyway) stream all rows from all tables at the same time. You could construct the SQL statement within the sequence (Routine activity) rather than in an exter...

Not without four or five separate lookups (the first word, the first two words, the first three words, etc.). And then you may have to handle DOUGAL, 5TH VISCOUNT MACABRE (i.e. not the "first words"). QualityStage can do all of that kind of stuff, though you may need to enhance the Classif...

OLETYPE is defined in the dictionary as field #2.

Therefore, assuming you've read the entire record into a variable called @RECORD, a suitable expression is @RECORD<2> or Field(@RECORD,@FM,2,1).