Transports from development to Test/Production

Question

Hi there,
While transporting objects from development to QA or Production, is there any way we can change the the name of the target staging database. For example, if TableA is the target table going to stageA database and when i move this object from development to QA or Production where staging database has a different name. So how can i handle this..should i have same database names in all the environments Dev, QA and Prod? i know we can do it manually changing staging database name one by one for each object but  how can we handle it if we have hundreds or thousands of objects?

Answer 1

You should setup and use multiple configurations on a single datastore. The whole point (well, almost the whole point) of the ability to setup multiple configurations, pointing (typically) at different databases, inside a single datastore is to be able to re-point a dataflow at a different database without recoding.  To "transport" from dev to QA, for instance, is as simple as either changing the default configuration of a datastore (from the dev database to the QA database), or making use of system configurations, which are just named sets of datastore configurations, which are, then, picked at runtime (or when scheduling a job). Of course, your schemas need to be essentially the same between environments.
Best wishes,
Jeff Prenevost