Balanced Optimizer & Operations Console

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
nvalia
Premium Member
Premium Member
Posts: 180
Joined: Thu May 26, 2005 6:44 am

Balanced Optimizer & Operations Console

Post by nvalia »

Hi All,

When we use Balanced Optimizer for SQL Push Down into the Database (Netezza in our case) will we still be able to get the Operational Metadata information from the Operations Console as we would expect to get for the Original (Pre BO) job?

e.g. I mean information like rows per link

Thanks,
NV
priyadarshikunal
Premium Member
Premium Member
Posts: 1735
Joined: Thu Mar 01, 2007 5:44 am
Location: Troy, MI

Post by priyadarshikunal »

Did you try balance optimization. I do not have access to 8.7+ environment but you should get the Operations details of the job after balance optimizer has been used. It may or may not be same as pre-BO but you should get the details of the new job.
Priyadarshi Kunal

Genius may have its limitations, but stupidity is not thus handicapped. :wink:
kwwilliams
Participant
Posts: 437
Joined: Fri Oct 21, 2005 10:00 pm

Post by kwwilliams »

Rows per link in a BO job that completely pushes the work down to the database would be pretty meaningless. Look at the example you are giving for performance tuning in another post:

Code: Select all

Row Generator -->  Neteeza
There is 1 link and the number of rows across the link is 1. Depending upon the database stage that is the target, there may be a number of rows deleted/updated/inserted in the job log.
Post Reply