DSXchange

Just trying to maintain my half-a-Ray posting rate.

It is meant for use in Server jobs. For PX jobs you have a 'Surrogate Key Generator' stage.

We know the client is on Windows. Ken asked because you marked your post with the OS as Windows and that is meant to be the OS of your Server. Hence the confusion.

(Doh! Late. That's what happens when you get interrupted)

No, they will only be there after a Client install as they are client tools.

There's nothing built into any current version other than 8.x, which is the first version where such a tool is available. As you've noted, however, you can manually compare two .dsx exports. Use your favorite file compare utility.

Doh! And here I thought you needed some of that goofy 'matches' syntax for this. That was too simple.

Of course, you need to design the job(s) properly to take advantage of this. A poor design can still give poor performance, even when bulk loading.

What is your target database? Why would you set your 'max' to 100 for a load like this?

I heard that Bulk Load doesnt improve performance much. Even some of the threads say like this.. You heard wrong. As an excercise, I just had one of my newbies convert a job from OCI inserts to the OCI Bulk Loader. Ray's favorite metric - rows/second - went from 600 to 15,000. Runtime went from 6.5...

And the first thing they'll tell you is XP is not a supported Server platform.

Try sliding your Columns over to the right and setting the last field's Incomplete column attribute to Replace. ... please let me know how you will slide through datastage What? Really? Ok, more details... Get to the Columns tab of the Sequential File stage. There's more to it than can display all ...

I left that for you, Ray.

Unfortunately, it's the right answer. I've been leading you astray here based on the Help documentation and the fact that I didn't take a moment to test what I was actually preaching. My apologies. It's not about the Exception Handler, per se. It's about the 'Automatically Handle' option. Here's the...

There's no such thing. However... there is a simple answer.

Create YASJ - Yet Another Sequence Job. Have it run SEQ1 and then SEQ2. Schedule the new job.

Well... let's see... you have a custom routine you are using 'before job' called InitialHashCreation and it doesn't exist in this Project.

If you just moved this job here, you forgot to bring the routine along as well. If not... someone may have removed it.

The manual does. How about you read the Containers chapter of the Designer Guide pdf and let us know if you have any specific questions?