We would like to use Version Control to manage our DataStage Server and PX jobs through different environments and versions.
However, our project contains a huge number of jobs (about 450).
Heard that VC can't manage more than 300 jobs. True or False?
Kasia
Version Control and number of jobs in a project
Moderators: chulett, rschirm, roy
False... and 450 isn't huge. One of my projects has almost 2200 jobs in it. Thank goodness for Categories.
Now, in all honesty, not all of them get versioned. A more reasonable comparison would be another project: 342 jobs, 1316 'versions' in VC. The only issue you'll see, much like the Director, is the refresh slowing down when a large number of jobs are involved. That and the initial connection and building of the VC 'view', especially if you are not local to the repository.
Other than that you shouldn't have any worries about what you are thinking about doing.
Now, in all honesty, not all of them get versioned. A more reasonable comparison would be another project: 342 jobs, 1316 'versions' in VC. The only issue you'll see, much like the Director, is the refresh slowing down when a large number of jobs are involved. That and the initial connection and building of the VC 'view', especially if you are not local to the repository.
Other than that you shouldn't have any worries about what you are thinking about doing.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
I've seen a VERSION project as big as 5200 components and am working with one now that has 2300 components (mostly jobs) and it still performs fine.
A common best practice though appears to be on occasion creating a second project called VERSION2 or VERSION_ARCHIVE and exporting VERSION to that one and starting again with a clean project with only the lastest and most likely needed components. That way you still have everything readily available but the main VERSION project is clean and performs well.
A common best practice though appears to be on occasion creating a second project called VERSION2 or VERSION_ARCHIVE and exporting VERSION to that one and starting again with a clean project with only the lastest and most likely needed components. That way you still have everything readily available but the main VERSION project is clean and performs well.
Byron Paul
WARNING: DO NOT OPERATE DATASTAGE WITHOUT ADULT SUPERVISION.
"Strange things are afoot in the reject links" - from Bill & Ted's DataStage Adventure
WARNING: DO NOT OPERATE DATASTAGE WITHOUT ADULT SUPERVISION.
"Strange things are afoot in the reject links" - from Bill & Ted's DataStage Adventure