DSXchange

Restarting the server is rarely a good solution. I would call that the "Windows way" and try to avoid the practice, unless there is some known issue that cannot be resolved... In case you don't know how to monitor the health and performance details on your server, then get with a server ad...

I personally do not know the answer but I suspect that it would not matter one way or the other. You initial tests show inconsistent results which probably just indicates the common real-world scenario that there is other varying workload activity on the database server and/or the DataStage server. ...

Can you narrow down the problem to say more specifically what is running too slow? Is it Server jobs or Parallel jobs? Is it all jobs or just a subset of jobs that read from a particular database, etc.? Is this a new server or a new problem on an existing server? Is to too slow all the time or just ...

If I had a 60 minute window and the job was taking only 5 to 10 minutes, then I may take a quick glance at tuning then quickly move on. What jumps out to me is that t he job startup times look pretty bad. What in the world is going on there? Have you got some slow before-SQL statements in your datab...

Upgrade to a version that has the workload manager (WLM) built in. It will protect your engine from overload when someone attempts to start 35 jobs at the same time. Various threshold settings are available. Jobs are automatically queued until resources become available.

I haven't tried it using DataStage but have had to query a SQL Server column that was named XML and stored XML but I do not recall the data type. It may have been TEXT or a string rather than the XML type.

SELECT [ID], CAST([XML] AS XML) FROM ...;

Yes, the Change Capture stage performs change data detection, but watch out... because "CDD" is another IBM product acronym for Change Data Delivery!

Thank you Vincent for sharing your healthy perspective and Craig for being the ever loyal supporting fan! You might need to get yourself one of those new IBM Cloud accounts to check out all these new additions.

I agree. It is a common misnomer. Clearly, the Change Capture stage would be abbreviated CC. CDC is different.

11.7 Fix Pack 1 is available to download.

Link: What's new in 11.7 Fix Pack 1

There are many new features listed by product, including several new connectors and expanded support of existing connectors.

The integration with GitHub sounds interesting.

Correct.

See also: IBM InfoSphere Change Data Capture

Also, if you want to help protect your ISD app and the size of the load on the network, then you can add your own logic into the job design. We did this on a few jobs that were similar in design to what you have described. You can count the number of records in the result set and limit the output to...

The pagination described sounds like it is unwanted behavior. Perhaps it is a defect. I have not run into that myself. I did run into large requests and results getting truncated back on version 8.7. We opened a PMR about it with Support. The workaround we used was to edit the properties of the ISD ...

Thank you for the additional pointers. Within the always-on ISD jobs, according to the score of each job we have a total of 224 processes running. As noted earlier, this box has 6 cores, so that averages out to always running at least 37 processes per core. Another surprise is that we found one job ...

We ran 8.7 and 11.3 clients from Windows 64-bit computers without this type of problem exactly. A problem we did run into sometimes was in attempting to patch the IBM clients while MCM had the other client version active. The problem you described could range from needing Microsoft/Windows updates a...