Archives of the TeradataForum
Message Posted: Wed, 03 Jul 2002 @ 15:47:57 GMT
AT&T Network Services uses Teradata for OTLP. When the decision was made in the late 80's, the driving factor was the open platform that Teradata provided. At that time, there were not many options for a database that was accessible from MVS and Unix.
All of the tables have fallback and we use journaling. The journals are dumped every hour. The tables are dumped twice a week.
Over the years we also had locking and performance problems, but most of those have been worked out. One of our systems has migrated from DBC1012 to 3600 to 5100M and in March we migrated onto a 4855. The other system still runs on a 3600 (hopefully to be migrated to the 4855 this fall!)
The reliability has been outstanding for the application running on the newer hardware (I can't say the same thing for the application on the 3600). In the past 2 years, we've only had 1 outage caused by hardware or software.
The performance is also very good. On the 4855, the transactions are flying. On the MVS side, the problem comes into that we have IMS transactions making calls to Teradata, therefore the overall transaction time from a user's standpoint is longer. On the Unix side, C or C++ programs make the calls to Teradata and network time is added into the picture.
Of course there is always someone looking at ways to move off of Teradata onto some other DBMS. The big driving factor is the cost of Teradata. But because of the immense development effort that would also be involved, it has not happened yet. In fact, the Teradata DBA's had a meeting with HP today for them to give a T & C to migrate the application to Oracle Parallel Server. I'm estimating at least $5 million.
|Copyright 2012 - All Rights Reserved|
|Last Modified: 21 Mar 2013|