Initially, we took the approach of a DS project containing all sequences and jobs and we would have them separated into categories/folders inside the project for each of the particular ETL streams. This worked for a while and may still be a good way to proceed but I am finding promotion time tiring as I have to select individual jobs (the modified jobs) to promote out of a huge list.
It has got me thinking about altering the structure so that each stream is in its own project with the project named to include the category. We have a development, test, and production area which each have their own projects to which the jobs/seqs are promoted using DS Mgr or Version Control.
For example:
We have "Aardvark" as a project and within the Jobs folder are categories -- "Alpha", "Beta", "Delta" -- within which are the individual jobs and sequences for each of those streams. When it comes time to promote to the test project using import/export of DS Manager, the combined set of jobs and sequences for all three streams gets very long and is annoying to search for the particular two jobs in the Alpha stream that were modified and need promoted.
Using this example, I would alter this to have three proejcts -- "Aardvark-Alpha", "Aardvark-Beta", "Aardvark-Delta" -- which would just have the jobs and sequences directly below the Jobs folder. Then, when it is time to promote, I will only see the list of jobs/seqs in Aardvark-Alpha rather than those for all three streams.
Thoughts? Feel free to weigh in. All opinions welcome.
![Smile :-)](./images/smilies/icon_smile.gif)