DataStage Deployment Strategy

JPalatianos · Post by **JPalatianos** » Fri Dec 08, 2006 8:32 am

Hi,
DataStage is a newcomer to our shop and we will be implementing our first production job in Jan 2007. The data architecture mangement team would like to create a strategy to roll out the tool for use by every application area(all accessing the same servers). My initial impression and recomendation was that development/support for the tool should be centralized to our group(DBA/ETL group). There are about 25-30 application areas in our shop and I am a bit concerned rolling it out to everyone.
Ofcourse management will do what mangement wants to do......but I was wondering if anyone has any thoughts/experiences with rolling out the tool in their shop.

Thanks - - John

WoMaWil · Post by **WoMaWil** » Fri Dec 08, 2006 10:03 am

DataStage is no Tool like MS-Excel, which you can roll out to everybody who can calculate that 1+1 is 2.

Don't give the product to anybody who hasn't had at least a 3-day-introduction into the product. Better is a one week training.

Don't give the product to anybody who doesn't work with product at least 10 hour on average a week.

DSguru2B · Post by **DSguru2B** » Fri Dec 08, 2006 10:14 am

Let DBA/ETL group be the owner of the application. Other application areas can get this groups resources to get their ETL work done. This way the control remains within one group. And that group will contain junior to architecture level resources who are comfortable with the tool.

ray.wurlod · Post by **ray.wurlod** » Fri Dec 08, 2006 3:54 pm

Set standards and best practices, and document them, before rollout. I agree with Wolfgang on the recipients. Require compliance with standards and practices, and punish transgressions.