Teradata Reviews

The two types of partitioning have been very significant for us - row and columnar partitioning.

With the current machine we are able to eliminate the use of OLAP cubes and allow customer queries to run directly on the Teradata machine.

We have now started running more profit generating activities on the Teradata machine, as opposed to just running reports, as in the past.

Data synchronization to the DR site.

My company’s management has to decide whether to invest in this area. This is more an internal issue at the company and definitely not a problem with the Teradata product. If we end up migrating to another platform, this will be the reason.

We have been using the solution for seven years.

Teradata is the most stable platform that I’ve worked with in my 20-year career.

Teradata’s scalability is excellent.

Teradata’s technical support is excellent. The support people are highly professional, and nice, to boot.

My previous background was with Oracle. I changed jobs and was asked to handle the Teradata team. It was a chance to learn something new and interesting.

Initial setup is quite straightforward, but previous experience with other databases tends to make it more difficult, because it takes a while until you get used to thinking in Teradata terms, rather than Oracle/SQL Server/PostgreSQL terms.

It’s a different animal. However, once you start thinking like a Teradata DBA, things are much easier.

Pricing can seem high, but when all factors are taken into account, the total costs are comparable to other databases as:

• Few DBA’s are required
• Unplanned downtime is very rare.

By avoiding the Enterprise solutions, you can actually end up with a cheaper, yet much more powerful machine. We moved from an Enterprise platform, to non-Enterprise and ended up with a machine that was 20X more powerful. We got an amazing performance boost.

Every few years we examine the option of migrating to other platforms such as HPE Vertica, Oracle Exadata, or SQream.

In the past, it turned out that other solutions, in order to provide the full range of abilities that the Teradata platform provides plus the migration costs, would end up costing more than Teradata does.

Make sure that you have a good Teradata DBA to help implement the solution. A great Oracle DBA is not sufficient, because it takes a while to internalize that they are two different things.

Make sure that you have a good backup/recovery/DR plan, and that it is covered by the infrastructure you are purchasing. Otherwise, you might find yourself with a system that performs great, but has no good DR solution.

The optimizer is the most valuable feature for us.

We are into DWBI (Data Warehousing and Business Intelligence) and Teradata is number one in the market for these solutions. They stood on top even for changing business needs and beat other competitors in benchmarking.

The Query Response time needs improving.

We have been using the solution for 12 years.

We did not encounter any issues with stability.

We did not encounter any issues with scalability.

I would rate the technical support at 9/10.

We never used a previous solution. In fact we migrated straight to Teradata.

There were a few ups and down with the initial setup but it's only one time during the initial phase.

Go for it.

It's already proven so we did not evaluate other industry solutions.

Go for it.

Each has its strengths and weaknesses; this is why we use a blended environment. We have a holistic view which is very mature and thus, it is impossible to give a concise answer.

However, converting the Teradata from a pure BI to an ODS has been our greatest achievement; it effectively has allowed us to remove over 20 portion copies of the data sets on other DB platforms for real-time operational reporting purposes.

It is the core of our fundamental real-time reporting and operational planning. It has saved us over eight figures in the operational run costs, improved data quality and consistency as well as reduced our overall infrastructure support requirements.

The increasing volumes of data demand more and more performance. I truly believe that in five years, we will breach the effective limits of Teradata to perform in a multi-petabyte environment, i.e., without significant changes to its underlying architecture. If this occurs, we will be forced to migrate to a more traditional platform (such as IBM Informix).

We have aggressively been using BI for over 20 years, with this evolving environment. Our most recent setup was about three years ago.

We have a broad range of BI and reporting tools, built on top of the Teradata Platform. It, currently, is the active Data Warehouse on 12.x , although we are migrating to 13.x after the New Year. This is supported by our IBM Congos (12), MicroStrategy (10) and the QlikView (12) reporting tools. We have also built extensive analytics on a Java base as well as some Microsoft BI integration.

We have had stability issues quite frequently, but this is mostly with the Cognos environment, as it is growing beyond its limits in terms of the active user access. This is why we are considering migrating significant portions of our over 4000 users to a coded environment in place of the platform.

Again as mentioned before, there were scalability issues in regards to Cognos and the over 4000 users in a single active environment.

Our in-house team is world-class, so we are not reliant on any external support.

We have moved from a distributed heterogeneous to a centralized homogeneous environment. Costs, data quality, sharing of information, and supportability were the reasons as to why we switched over to Teradata.

The setup took place too long ago to remember.

Negotiate, negotiate, and negotiate some more. But long before you start to have a clear understanding of your direction, use patterns and check the roles that BI plays in the organization. Make sure you have the in-house skills to design and support the solution, as relying on external sources is extremely costly and tends to lock you into specific platforms, tools, and paradigms.

We did a six-month review of potential candidates and options. Every three to five years, we re-evaluate the selection criteria and re-open the solution's design with an invitation to the vendors to offer an alternative. The process consumes about three months, but it has allowed us to keep current and, more importantly, to leverage off the process so as to ensure that we are getting the best value for our money.

This comes back to understanding the what, why, and how of the solution. Once you understand that, then plan it accordingly and ensure you have sufficient time to address any of the surprises that could occur.

Each tool fills a niche and is used accordingly. I doubt if there is anything perfect out there, as each tool has its own considerations when being deployed.

Our greatest concern with Teradata is the performance impact of the OUTER RIGHT JOINS across a petabyte environment.

Viewpoint, the detailed query logs and performance statistics are valuable features. As a specialist for Teradata Performance, I find this data valuable for system tuning and query tuning.

Our enterprise data warehouse (EDW) runs on Teradata and it is the single version of truth for management decision-making and reporting.

The SQL Assistant is very basic. This tool can be improved for usability.

I have used this solution for around ten years.

There were no stability issues.

There were no scalability issues.

Technical support is good.

We have used Teradata since day one.

The setup was complex, but the work was outsourced to the Teradata Professional Services.

Teradata is not cheap, but you get what you pay for.

A cost-benefit analysis (CBA) needs to be done by the customers so as to make sure it serves the intended purpose.

Have a long-term vision, the ROI will not come in the short-term.

A cost-benefit analysis (CBA) needs to be done by the customers so as to make sure it serves the intended purpose.

Throttle

Columnar

Faster query response time.

Concurrency is still a challenge, pricing is still high.

Three years.

No.

None.

Yes.

6/10

6/10

Oracle. We switched because of TD distributed architecture and it is the best product for EDW.

Done by Teradata PS.

Teradata PS.

• The ability to process large amounts of data very quickly
• Its adaptability

Our business processes are much more efficient with Teradata's speed.

I'd like to see better processing on a transactional level and star schema optimization.

I've been using it for 13 years.

No issues encountered.

No issues encountered.

It's excellent, 10/10.

It's excellent, 10/10.

No other previous solution for these applications was used.

It's complex in terms of physical data modeling.

We used a hybrid team of both in-house staff, and a vendor team.

It's more than 100%.

It's not cheap but definitely worth it. It's been chosen by companies that tried cheaper solutions.

We also looked at DB2.

Know your data.

• It is simple for me as a developer
• Query tuning is simple.

It's simple to use and scalable.

I've used it for eight years.

No issues encountered.

No issues encountered.

No issues encountered.

We used a vendor team who were 7/10.

The speed has been increased.

We also looked at Hadoop.

It's simple but costly. However, this doesn't concern me as I have to develop applications. My employer can give me any product and I will learn and develop with it.  Almost all database products are 80% same.