Killing a Fly with a Atom Bomb
April 13, 2017
Killing a Fly with a Atom Bomb
Overall Satisfaction with Teradata Database
Teradata was used as a staging area for SAP financial information. It was set up as a enterprise wide data warehouse where anyone (with proper access) could come in a grab standardized financial information. As a user of the database our job was to pull information for reports and feeding our down stream applications. Using multiple SQL GUI interfaces we tried to pull our information, however the database could not handle some of the most basic Select statements. Now, one could say that the engineering and design was not up to par but I have seen other databases (Oracle) that have been setup incorrectly still be able to handle a simple select statement.
- It is easy to navigate.
- Using the GUI you can build SQL if you don't know how.
- The interaction for Projects can be managed in the GUI.
- Speed. Seems slow and clunky
- Make it user-friendly from the implementation side of the house.
- Improve the table mapping feature.
- Negative impact is again the slowness that would be felt by developers and users.
- Negative impact is that there is a learning curve if they have been using any other type of SQL.
- Positive impact is that you can collaborate with other developers by using projects.
Oracle seems to have the upper hand. Oracle takes fewer resources and is harder to get wrong because the user has a very detailed install instructions and wizard to follow. Teradata has a place where you can store projects and collaborate, but so does Oracle. Teradata GUI has a way to build SQL if you don't know how, but Oracle has that as well. Building a view to do complex slicing of data is not the most intuitive in Teradata. Oracle views can be optimized and have meaningful functions that can be added to them.