Do we need a separate database for each ETL server?

A forum for discussing DataStage<sup>®</sup> basics. If you're not sure where your question goes, start here.

Moderators: chulett, rschirm, roy

Post Reply
bharathappriyan
Participant
Posts: 47
Joined: Fri Sep 23, 2005 6:01 pm

Do we need a separate database for each ETL server?

Post by bharathappriyan »

Hi,

Do we need a separate database for each ETL server?. In my project, two schemas are created instead of two ETL servers. Why do we need to have two schemas or databases for two etl server?

Thanks,
Bharathappriyan
kduke
Charter Member
Charter Member
Posts: 5227
Joined: Thu May 29, 2003 9:47 am
Location: Dallas, TX
Contact:

Post by kduke »

They name the schema XMETA. Not sure you can rename it. So it requires different databases. That is the only reason I can think of to force different databases.
Mamu Kim
bharathappriyan
Participant
Posts: 47
Joined: Fri Sep 23, 2005 6:01 pm

Post by bharathappriyan »

Hi kduke,

Thanks a lot for your reply.

We are using DataStage 7.5 version as well. Does't it have XMETA? My understaning is that from 8x onwards we have that XMETA schema if i am not wrong.

Thanks,
Bharathappriyan.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Anything less than 8.x does not have an XMETA repository.
-craig

"You can never have too many knives" -- Logan Nine Fingers
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Best practice is to have one WAS instance and one XMETA database to control as many engines as you have. Or, perhaps, one for production and one for all non-production environments.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply