What is our primary use case?
We primarily use the solution for data warehousing.
Primarily what happens is, in Juniper, they have internal business analytics and intelligence, a business intelligence analytics dashboard, and a lot of databases that capture the customer feedback.
It actually captures all the internal defects that are tracked on products. There are different databases that accumulate all this data. Basically, you need to be able to source the data and do some filtering. We extract, transform, and load logic. We have to run certain business rules based on what the program or management team looks at. The teams want to filter out some of these problems that they have, and they want to analyze how well the company is responding to many of these customer issues, et cetera.
Our company is a large company with each particular team using its own database and its own database tables. It becomes extremely hard for the company to take the data from different data sources and be able to correlate everything and be able to analyze many of the processes that are happening within. There is a workflow discontinuity that has been observed due to the fact that the data is distributed. In order to understand exactly how a request comes in from the customer and what goes on behind the scenes in order to resolve the problem or to be able to provide the support to the customer, and how long does it take before the problem gets fixed and delivered, et cetera, we need to centralize everything and we use data warehousing for that.
There are other similar kinds of business rules filtering that happen on the dashboard as well. This enables people to be able to view the data that is needed and the metrics that are of interest to them and is especially useful when it comes to the executive team.
What is most valuable?
The most valuable feature is the ability to be able to access the different data anywhere, and the Cloud Data Warehouse solution enables that.
To be able to extract, transform, and load logic, and also to be able to correlate the data in different databases and not just correlate it in one is great.
If I want to be able to perform certain database queries on a joint operation between database tables located on two different database sources, et cetera, I can do that.
The most important thing we get out of the product is the intelligence that we derive. How the company feels in terms of process efficiencies is positive. In order to understand how a workflow is actually executed within the company, we need the assistance of this product. That's where the maximum value comes from.
The ability to access the data from a website or from anywhere is very important. The people themselves can also be anywhere.
The licensing system enables the company to track how a switch is used by an end customer, an end-user, and what different features the customer is actually running. It tells us a lot about the product. You have a lot of quantitative data that can provide an understanding of people's behavioral patterns and people's usage patterns when it comes to understanding what features or what are those elements that customers are most interested in - that can be tracked.
The solution is stable. The product is reliable.
The scalability is good.
Technical support has been good. They are helpful.
What needs improvement?
In terms of improvements, I can only speak from the dashboard perspective.
The most important thing is that I don't know how far the dashboard integration goes. People, for example, were using the Cloud Data Warehousing product, however, they were actually building their own dashboards, et cetera. That's like double the amount of work. The company should have the ability to integrate with something like Tableau to make everything more standardized.
With the customer data, we were able to integrate very successfully with Tableau and we were able to use it well from an end-user perspective. We were using the Tableau interface for understanding what our customer buys, et cetera. For example, for the customer financial data aspect of it, the business data, we were able to use Tableau dashboards. It would be better to use back-end data warehousing and also have dashboard reporting and have everything integrated properly. It doesn't need to be Tableau. It can be some other dashboard. However, it needs to be standardized.
The usability could be a bit better. It could be a bit more user-friendly.
For how long have I used the solution?
I've been using the solution for five or six years or so. We've used it for a while.
Buyer's Guide
Teradata
December 2024
Learn what your peers think about Teradata. Get advice and tips from experienced pros sharing their opinions. Updated: December 2024.
830,526 professionals have used our research since 2012.
What do I think about the stability of the solution?
The solution does seem to be a quite stable solution. We haven't had any major issues that I am aware of. Generally, stability has never been a problem with the product. There are no bugs or glitches. It doesn't crash or freeze.
What do I think about the scalability of the solution?
The scalability seems to be pretty good. If a company needs to expand it, it can do so.
How are customer service and support?
Technical support is decent. We are satisfied with the level of support we receive.
Which solution did I use previously and why did I switch?
Some time ago, we also implemented SAP internally within the organization. For some reason, there was a decision not to go with the SAP HANA. I don't know why that decision was taken. Likely, it had to do with the kind of data or the kind of use case that we had and the data sources that we had. Teradata was considered to offer better performance and was a better-performing product.
What other advice do I have?
Teradata definitely does what it says, in terms of an on-demand platform, as it's a cloud service and it is definitely scalable. It's secure and it does provide scope for a lot of automation. The provisioning part of it, the administration and backup recovery as well as the analytics are some things that could be integrated in a more advanced manner. Maybe certain enterprise use cases need to be included so that users in an enterprise environment can build an analytics dashboard out of it. Support is good, however, the support requirements are not too much. Overall, the usability can be a little simpler. In general, we've been satisfied with it as a product.
I would rate the product at an eight out of ten. I want to be a little bit conservative in my rating as I want to be sensitive to the fact that people really want to be able to do the slicing and dicing of data at a user interface level and to be able to see all the insights at once. At that level of usability, to be able to slice and dice, you need to give a dashboard to a user.
If, for example, I have a certain type of organization that has a hierarchical organizational setup, I should be able to slice it to a specific group or a specific department, or a specific team. I should be able to see the metrics corresponding to that, or corresponding to the drilled-down data. While that's possible today, what I'm trying to say is that to be able to do it as a business user, to be able to use an interface in order to be able to do that kind of custom slice and dice operation and see the data in real-time, people are looking for more. Users want a level of usability from a business rules perspective, et cetera. That's something that people are looking forward to from intelligent and smart dashboards. It just needs to offer something that is much closer to capturing real-time information.
Disclosure: I am a real user, and this review is based on my own experience and opinions.