Teradata Reviews

We primarily use the solution for the EDW. 

The performance is the key item we appreciate. We're able to easily trigger jobs and we have access to integrations for running jobs. It's easy to use for the most part, which is why I really like it.

It's stable and reliable.

I've never had any issues with scalability.

The initial setup is pretty simple to set up. 

Apart from Control-M, it would be nice if it could integrate with other tools. Specifically, with respect to the integrations with the automation tools, if that can be increased, and if the tester could be able to test more automation scripts in a better way it would help. The efficiency could always be increased.

Occasionally, at the outset of the implementation process, we struggled a little bit.

I've only used the solution for a few months. It hasn't been a year yet. It hasn't been that long. 

The stability has been good so far. It's reliable and the performance is good. there are no bugs or glitches and it doesn't crash or freeze. 

The solution seems to be scalable. I've never run into any issues with sizing. It's good.

I cannot recall the exact number of users that are on this solution currently. 

Technical support is quite good. We used them once or twice and, as I recall, their response was always very quick. We are quite satisfied with the level of service they offer. 

For the most part, the initial setup is good. We found it pretty straightforward. That said, sometimes, in the beginning, we struggle. 

For us, the deployment took around two hours. It didn't take too long. 

We had about ten members on the technical team that handled deployment and maintenance. 

We are able to handle the initial setup ourselves. As long there are not some prerequisites or system issues, then it's possible for us to handle everything.

I don't have any direct details about the licensing or pricing of the solution. 

I'm not sure of which version of the solution we're using. It might be a previous version. 

I'd recommend the solution to other users and organizations. 

I would rate the solution nine out of ten. We are quite pleased with its general capabilities. 

The most valuable features are the large volume of data and the structuring of the data to optimize it and get very optimal data warehouse solutions for customers.

An area that needs improvement is the cloud-based version of the solution because it's designed for on-prem and then transferred to the cloud version. Teradata needs to pay attention to the cloud-based solution to make sure it runs smoothly. In the next release, I would like Teradata to be cloud-agnostic in order to not limit customers' choices.

I've been using this solution for fifteen to twenty years.

Teradata is superior, stable, and has no problems.

Teradata is easily scalable. 

The setup is complex and requires specialized people for implementation.

The cost of running Teradata is quite high, but you get a good return on investment.

I've also evaluated Snowflake, which allows you to expose your data to multiple sources for monitoring without additional work.

For the on-prem solution, there isn't really anyone who can compete with Teradata. I would rate it as eight out of ten.

We use Teradata in our data warehouse and we extract data. We have a data department that uses many tools for data extractions.

Teradata has good performance, the response times are very fast. Overall the solution is easy to use. When we do the transformation, we have all of our staging and aggregation data available. 

Teradata could improve by providing better training. For example, Oracle provides good overall training. It is not easy to find information on the internet.

I have been using Teradata for approximately eight years.

The solution is stable. However, there are times when we are using large amounts of data and we can see some latency issues.

Teradata is scalable. We have two large servers and if we need to add new servers it can be done. Additionally, adding hard drive space or more performance is not a problem.

We have approximately 15 users using this solution in my organization.

The technical support is good but they could improve because sometimes they can take two weeks to resolve issues.

The implementation took approximately one month.

We did the implementation of Teradata using their support.

The price of the solution could be reduced, it is expensive.

I would recommend this solution to others.

I rate Teradata a nine out of ten.

My current use case is an analytical system for an oil and gas company. They have a data lake and they are getting their data from different IoTs and different SAP systems. They wanted to have some feedback about their system and check on their production.

The IoT center's data was actually our use case, then how we can use that data to prevent disaster from happening. Previously, this work was all done manually. If there is a leak in the pipes then it is a large area to search because there are hundreds of kilometers that have been run.

To tackle this problem, they use IoT sensor data. It helps them to understand how the flow is working at a specific point in time, what happens when they're drilling the oil and other types of data. To complete the analysis, we use an analytical system or a Teradata Azure system that we designed.

The ECL was designed in a manner where we were doing the transformation on Hadoop. It is more like a balanced system where you use Hadoop for what it is good for, and where you use Teradata for its purpose.

I have worked in several different environments. The largest Teradata implementation on Azure was done by me. Right now, I'm working with AWS but previously, I have implemented both on-premises and hybrid deployments.

Performance-wise, Teradata beats everything.

The flexibility in design is very good.

When you want to tune it, it is very easy to do. I have worked a lot as a DB and I know that when there is a query that is stuck for hours, and you want to tune it, the task is quite easy. You can use the indexes and architecture, and exploit the power of Teradata.

There are lots of improvements that Teradata is working on and many that have already been done. However, recently I was in a session with people who are working on the data sciences side of the business. The data science group is not using the Teradata modeling features. Rather, they are using third-party tools for the prediction and forecasting models that they are building. Teradata should focus on functionality for building predictive models because, in that regard, it can definitely improve.

In my experience with Teradata, I have seen their sales strategy and that needs to change. As an organization marketing a product, they need to be cloud-focused instead of the on-premises thinking that they currently have.

There are a few things where you are totally dependent on the customer service and support from Teradata. This is an area where they really need to improve a bit, especially when you're talking about cloud service integration. Depending on the environment you may need to contact the AWS team, or the Azure team, or the GCP team, or the Teradata team. In all of these environments, improvements need to be made.

I have been working with Teradata for more than a decade, probably close to 11 years. I have been in the industry for approximately 18 years.

We are satisfied with the stability.

It is quite easy to scale. For a cloud-based deployment, it's even simpler now.

Previously, it was easy if we just wanted to add power but there was an impediment when you had to add a node. Similarly, it was difficult when you had to shift to the newer nodes. Now, however, with the cloud, it's easy to do.

For the on-premises deployment, a lot of people consider the initial setup to be difficult. Keep in mind, however, that Teradata is a million-dollar product, so they set it up for you.

For a cloud-based deployment, it is now pretty simple to deploy.

The price of Teradata is on the higher side, and I think that it where they lose out on some of their business. The price should be reduced to make it more competitive.

One of my clients recently tried to switch solutions but they have rolled back to Teradata. The same thing happened with another company that I know of in Pakistan, where they tried working with an IBM product.

My advice for anybody who is implementing this product is that they really need to hire the right people. Get people who actually have worked on Teradata to guide them.

You can buy Teradata and you can get it up and running, but until you hire a few good people, you are not going to get the full benefits from it. These people are not resources that you would ask Teradata to provide you. Rather, you can hire them from the market.

The important part is that you need to have people who have good experience with Teradata because they can truly exploit its power for you.

Overall, this is a good product. It is close to the best but I cannot rate it perfectly because of the price.

I would rate this solution a nine out of ten.

Improved performance of ETL procedures, reporting. Decreased efforts, time, and number of staff supporting DWH.

• Scalability
• Functionality
• Performance

GUI of administrative tools is really outdated.

Nothing major, as far as I can recall.

No issues, scalability is a key feature of Teradata.

Support is on par with other vendors.

We used Oracle. Scalability and performance were the reasons we decided to try Teradata.

It was easy, the whole job was done by Teradata.

It is still a very expensive solution. While I very much like the pure technological supremacy of the software itself, I believe Teradata as a company needs to become more affordable. They are already losing the market to more flexible or cheaper competitors.

We did performance testing. We had a set of real life MicroStrategy reports. Our conditions were: Not allowed to redesign data model, not allowed to rewrite the queries, all queries should be generated by MicroStrategy, no aggregates. Teradata appeared to be way faster than a similarly configured (in terms of hardware) Oracle server.

Go with the Enterprise series and don't waste time and money on 25xx. Sooner or later you will migrate anyway, so don't even start with departmental solutions.

I mainly used Teradata as an EDW and for customizing and integrating CLDM, applying aggregation in the database, and analysis.

Teradata's best feature is its speed with historical data.

Teradata's UI could be improved.

I've been using Teradata for about four years.

Teradata's stability is good.

Teradata's scalability is one of its best features.

Teradata's licensing is on the expensive side.

I would rate Teradata nine out of ten.

As a contractor for various companies working in various industries, we usually find Teradata in financial organizations. It is often being used for relational data storage for huge data warehouses (usually built on Inmon principles) or as storage for building analytical data marts. Teradata is positioned as a high-performance solution for heavy analytical queries and, in fact, it is. Moreover, Teradata is typically supplied with the whole ecosystem of its tools (like Viewpoint), but I have not extensively used them.

• Cuts time to process huge amounts of data with analytical queries
• A conventional and easily defined way to build a data warehouse or a layer of data marts
• Better development time - Teradata can be easily used in ETL mode transformations, so there is no need for expensive and inconvenient ETL tools

Efficiency of running analytical queries. Teradata was mainly invented for that purpose and it really does it well. We were able to migrate the code from SAS analytical platforms to pure Teradata and got an order of magnitude of performance growth (taking into account that the hardware was similar).

Query language and its functionality are rather limited, compared to Oracle or even SQL Server. However, it is possible to perform any kind of logic in it (though some workarounds may be required).

Data ingestion is done via external utilities and not by the query language itself. It would be more convenient to have that functionality within its SQL dialect.

We have not experienced any stability issues.

No. Teradata is positioned as a rather scalable system, and we have not seen any issues with it.

I was not impressed by tech support. We made several requests regarding performance issues we had with our applications but did not get helpful answers.

It is hard to say what our clients had been using before. It is safe to say that this was their first option for analytical data warehouse implementation.

I cannot say for sure. We have not taken part in deployment activities. As it is an appliance, I expect it is a bit complex.

Price is quite high, so if it is really possible to use other solutions (e.g. you do not have strict requirements for performance and huge data volumes), it might be better to look at alternatives from the RDBMS world.

Usual alternatives in the same segment for our clients are Oracle Exadata, SAP HANA, and Hadoop.

I rate it an eight out of 10. It is definitely the best RDBMS I have ever worked with, in the sense of building a data warehouse. It is fast, and easy to use in terms of writing queries. However, you have to understand the specifics of the data storage and its technical architecture, which is not typical for an RDBMS.

In terms of advice, I would suggest your provide training for your personnel, because it is rather important to understand the technical specifics of Teradata to create efficient solutions with it. Other RDBMS's usually requires knowledge  of generic theory, but that will not work with Teradata.