on 10-16-2014 4:44 AM
Is it a good practice to use a SINGLE central repository for ALL projects in a company?
Hello
There is no right or wrong on this. In a small organisation, a single central repository could work. If you have totally separate projects, you could configure a central repository for each project. The number of local and central repositories can be configured to whatever suits.
Personally, I NEVER use central repositories to promote code, I only use them within the development environment. I always use ATL (packaged with DDL, etc.); it is quicker, less error prone, and more secure.
Michael
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Eduard,
thank you for your reply,
but actually the question is not about three tiered landscape, there are no doubts that it is a good thing.
I would like to know if it is a good solution to have jobs, dataflows etc. from different, not connected with each other projects in the same central repository? Or is it better to have a separate set (dev, test, prd) of central repositories for each project?
User | Count |
---|---|
81 | |
25 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.