Wanted to check what are the various ways people are using. Considering we have a DEV and PROD environment, what should be the process?
1> Have one catalog and have it populate DEV and PROD DB?
2> Have two catalogs, one for DEV, one for PROD and then migrate the changes from DEV to PROD catalog after a QA?
If so, do both the catalogs reside in one DB or both should reside in seperate DBs?
3> For any kind of manual data fixes, should the data from PROD be copied to DEV , fix in DEV, test it and then move the data
fix to PROD or execute a proper script in PROD to fix it?
My current client has a cognos implementation which is upside down and no change management at the moment. Everybody
works in PROD and nobody knows more than 20% of the subject :)
Hello
We have 2 env (DEV, SVT) for DEV and test. We have 2 different DB to install catalogs separately.
Same for UAT and prod. The strategy is as below:
1. Dev for all dev (change/Bug fixes)
2. SVT is always the same we have in UAT and Prod.
In case we have to deliver data fix in Prod, we make changes in SVT and Test in UAT and then in Prod. This is more concern of release management . In case of data fix, we have created a job that runs every time we import catalog in any of the env. Thus data fix is delivered he same time and corresponding Jobs are delivered.
ideally we should separate all the env as change capture in Data manager is quiet difficult that other etl tools.
Dilsher
Thank you Dilsher. I am also thinking of having 2 environments and 2 catalogs for DEV and PROD in separate databases.
That helps.
Thanks again,
Ashok