DSXchange

Run the job from a Job activity. Store the value it retrieves in the job's user status area. Access that value downstream of the Job activity using the $UserStatus activity variable. Make your comparison in a Nested Condition activity to determine whether or not to trigger execution of the other job.

Welcome aboard. :D Instructions from the Forum: Post ideas, requests, and comments regarding content and structure of the FAQs forum here. You should have posted in the General forum. This particular forum has a specific purpose. Search DSXchange should be your first approach. We are also striving t...

Most of those rumours, in my opinion, were started by sales people who - if one were being generous - were not aware of the truth or - to be less generous - realized that the commission/recognition is far higher if you sell Enterprise Edition.

Did your job abort? Chances are that your Lookup stage has the lookup failed rule set to "Fail" (its default value).

NO, because you need a connection before any set command is honoured.

Are you using write cache? Are you using shared hashed file?

Convert the "T" to a space in your string using Convert() function, because your default timestamp format string has a space between the date and time components.

Sorting is guaranteed to be preserved unless you repartition the data. Your first option would require a Join stage rather than a Funnel stage, otherwise you'll get three copies of each source row. Your second approach (all in one Transformer) may be quite efficient - make your derivation expression...

I bet your DBA was not using ODBC protocols. So why are you? You have the choice of "native" client interface, or using bulk loader.

Sequential File stage ---> Transformer stage ---> XML Output stage. Depending on exactly what you want to do you may need a target Sequential File stage as well.

Assign the job's user status to a user variable using a routine that invokes DSAttachJob(), DSGetJobInfo() and DSDetachJob(). Only if the job whose user status you require is upstream in the same job sequence can you use the activity variable $JobStatus.

Or, indeed, a DIGITS Transform.

Given the original problem I'd use a DIGITS Transform.

In the table definition the Display Width is the actual width used in the file. This can be accessed as the Field Width property in extended column properties (Edit Row from the Columns grid).

There are many different kinds of CDC (change data capture). Ideally the database itself will maintain a log of deleted records, perhaps via a trigger or through the application itself, and you can leverage that. Some CDC tools inspect the transaction logs. Comparing periodic snapshots of the tables...