Version Control and number of jobs in a project

kasia · Post by **kasia** » Mon Jan 10, 2005 8:29 am

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

chulett · Post by **chulett** » Mon Jan 10, 2005 9:03 am

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.

datastage · Post by **datastage** » Mon Jan 10, 2005 9:12 am

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.

chulett · Post by **chulett** » Mon Jan 10, 2005 9:27 am

Good point. Something that VC in 7.x has eased is the use of multiple Version Control repositories for people with multiple projects across 'subject areas'. I currently have 4 'VERSION_xx' projects servicing 12 projects.