How to handle different DB schemas for Dev, Test and Prod

deepbanerji · Post by **deepbanerji** » Tue Nov 22, 2005 4:08 pm

I have different database schemas for Dev, Test and Prod. When I export my Jobs to Test, Do I need to import new table definitions from the Test Schema and update my Queries in all the jobs or is there any other way to handle this situation.

Thanks,
Deep.

ArndW · Post by **ArndW** » Tue Nov 22, 2005 4:12 pm

The usual approach is to put values that can (and should) change into job parameters - things like file paths, DB userids/passwords/schemas/instances.

ketfos · Post by **ketfos** » Tue Nov 22, 2005 4:30 pm

Hi,
You need not import your new table definitions into datastage from TEST schema after you have moved the jobs from Dev to Test enviornment.

You should able to run your job from TEST enivornment after moving from DEV - VERSIOn CONTROL - TEST.

Ketfos

kcbland · Post by **kcbland** » Tue Nov 22, 2005 10:37 pm

Never use fully qualified schemas, rely on synonyms. If a schema is needed, use job parameters. On the table names, leave off the schema and make sure you alias the name of each table without the schema name so that the DERIVATION column in the definitions is correct.

vmcburney · Post by **vmcburney** » Tue Nov 22, 2005 11:20 pm

Avoid anything that requires a modification and recompile of your job in testing or production. Any job property that you need to change to get it to work in testing should be changed to a job property. This includes database details and file paths. You can change job parameters without recompiling the job.

rleishman · Post by **rleishman** » Wed Nov 23, 2005 1:00 am

Are you using 7.5.1A? Is, read this.

rkdatastage · Post by **rkdatastage** » Wed Nov 23, 2005 1:05 am

Hi

you can use job parameters which can implies to the database connection , user id , password. its better to use dynamic parameterization rather than static parameters

RK