one project or multiple
Posted: Thu May 22, 2008 6:54 am
Hi,
At this moment we have a 7.5 environment with one big production project (3000+ jobs and flows). Untill now we haven't had any issues with this size.
I'm now planning a move to a datastage 8 environment (it will not be an upgrade, it's a new install on new hardware, new DB,...) and I thought this would be the time to make a decision about splitting this project or not.
What do you consider the biggest advantages or disadvantages of having multiple projects? Is there anything new in DS8 that has an impact on this?
Reasons we kept it in one project:
- routines, jobs, flows that are used in a lot of flows are kept in one location.
- easier to work with lookups and datasets.
- no overhead of importing source metadata into all projects.
At this moment we have a 7.5 environment with one big production project (3000+ jobs and flows). Untill now we haven't had any issues with this size.
I'm now planning a move to a datastage 8 environment (it will not be an upgrade, it's a new install on new hardware, new DB,...) and I thought this would be the time to make a decision about splitting this project or not.
What do you consider the biggest advantages or disadvantages of having multiple projects? Is there anything new in DS8 that has an impact on this?
Reasons we kept it in one project:
- routines, jobs, flows that are used in a lot of flows are kept in one location.
- easier to work with lookups and datasets.
- no overhead of importing source metadata into all projects.