What are the best practices when it comes to deciding between a mainframe and NT environment for a data warehouse? We have a mainframe in house for OLTP and can use it. Are there ETL tools on a mainframe?
David Marco’s Answer:: There are several ETL tools available on the mainframe. Evolutionary Technologies International (ETI) has the leading tool in this environment. Informix owns a tool called Prism Warehouse Executive (PWE) that also works well on a mainframe.
Doug Hackney’s Answer: The greatest challenges in the mainframe environment are cultural. A data warehouse is a relatively freewheeling environment with multiple roles needing the capability to create and drop temporary and permanent table including users. Mainframe environments are also challenged to deliver sustained high performance to DW tasks at the most critical times (i.e., month, quarter and year-end) as BI is always the lowest priority behind OLTP jobs. If you can gain dedicated processing power and overcome the imbedded cultural biases, mainframes have plenty of power to do the job. Your choices of ETL tools will be limited to first generation code generators such as ETI and Prism/Ardent/Informix.
Chuck Kelley’s Answer: In DM Review magazine back in May, 1994 there was an article by Bill Inmon and myself that described the 12 defining characteristics of a data warehouse. The first characteristic is that they are separate but equal. In that sense, I would recommend (based on your two options, though there are more) using the NT environment instead of the mainframe that is also hosting the OLTP system. I realize there are extra cycles available on the mainframe, but how do you tune an operating system to do both a) 5 reads, 7 writes typical OLTP system, and b) read a million rows and aggregate? If you are running MVS, you can run two "copies" of MVS on the same machine, but that is, in effect, the same as getting another environment.
Now it would be very wise to use those cycles to do the ET part of the ETL process. There are tools that run on the mainframe. The ones that hit my mind are Warehouse Executive by Ardent (www.ardent.com) and Tapestry by D2K (www.d2k.com). I know that there are more.
Sid Adelman’s Answer: There are more tools available for NT than for the mainframe, and these tools have usually had more field exposure and testing. Tools for NT will most likely be less expensive, but the mainframe is far more scalable, has better availability characteristics and has better monitoring tools. Be sure to look at the skills available to you. This could be the deciding factor.
Register or login for access to this item and much more
All Information Management content is archived after seven days.
Community members receive:
- All recent and archived articles
- Conference offers and updates
- A full menu of enewsletter options
- Web seminars, white papers, ebooks
Already have an account? Log In
Don't have an account? Register for Free Unlimited Access