DSXchange

I wouldn't even give it a shot on a machine with only 512 MB of ram. WinXP will take up 200MB or so of that.

What is the question?

Which DB engine are you using?

Or, going forward, does it really matter if it takes a couple seconds extra to process 10 records? I'd stick to parallel jobs going forward unless there is a compelling reason not to given that is the direction IBM is heading with the product (legacy support for Server jobs but no new development).

The license file will be provided by your IBM rep...Check the email with your license codes for an attachment.

Enterprise - Parallel read and ability to lookup data in tables using Lookup stage. Must have DPF installed on DB2.

API - sequential read and no lookup ability. A basic stage for reading data.

I would consider any logical areas for a split if you wanted one. For instance, you could split by target systems or subject areas. I'm not a big fan of multiple production projects as it leads to more areas for code to get mis-migrated.

Agree with Ray though, sounds like you have a solid plan.

The aggregator is known to choke under large volumes of data. Check space and rearchitect the job if necessary.

Maybe because you can't Trim a null character? Did you try using TRIM(IsNull(in.ABC,0))?

This happened to me once too. Try using the Plug in Meta data extraction versus ODBC.

Hi...i have a job created for updating a column in the oracle table. The job got aborted in the middle while updating. Is it possible to update from the point where it got aborted?. The commit interval is for every 2000 rows. Not with a commit interval like that. You have to start from the beginnin...

Try using type Numeric in SQL Server instead of Decimal.

Try and import through Manager.

Sounds to me like a DB connection issue.

Use ODBC Stage

SQL Server can ONLY be installed on Windows platforms.

Performance is in the eye of the user.

What's fast to you is slow to me, and v/v. Provide some performance numbers and target numbers and we'll talk.