COGNOiSe.com - The IBM Cognos Community

ETL, App Development and other tools => COGNOS DecisionStream/Data Manager => Topic started by: WayneVaughan on 27 Sep 2010 06:10:18 AM

Title: Data Manger Catalogues
Post by: WayneVaughan on 27 Sep 2010 06:10:18 AM
New to Cognos Development.

I'm currently developing solutions using a single Data Manager catalgoue. To populate the development,testing and production databases I simply change the connetion properties to point to the desired database.

Is this approach the correct technique or should I have seperate catalgoues for development,testing and production?

What are the benefits of a multiple catlogue approach?
Title: Re: Data Manger Catalogues
Post by: MFGF on 30 Sep 2010 01:07:16 PM
Hi,

Generally I've tended to keep my Dev, Test and Live catalogs separate.  This then allows me to begin work on builds in DEV without affecting how the builds run in TEST and LIVE.  When I'm ready to deploy, I export the DEV catalog and import it into TEST, then set a test programme in place (again without affecting the LIVE builds).  I can then continue to work in DEV without affecting TEST or LIVE.  Once I have proved that TEST is stable and provides desired results, I export the TEST catalog and import into LIVE.

Regards,

MF.
Title: Re: Data Manger Catalogues
Post by: WayneVaughan on 01 Oct 2010 03:05:47 AM
Thankyou very much for your reply.