Comparison Buyer's Guide

Executive SummaryUpdated on May 29, 2022
 

Categories and Ranking

Snowflake
Ranking in Data Warehouse
1st
Average Rating
8.4
Number of Reviews
95
Ranking in other categories
Cloud Data Warehouse (1st)
Teradata
Ranking in Data Warehouse
3rd
Average Rating
8.2
Number of Reviews
55
Ranking in other categories
Relational Databases Tools (7th)
 

Market share comparison

As of June 2024, in the Data Warehouse category, the market share of Snowflake is 16.5% and it decreased by 9.4% compared to the previous year. The market share of Teradata is 15.6% and it increased by 9.8% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Data Warehouse
Unique Categories:
Cloud Data Warehouse
30.6%
Relational Databases Tools
5.9%
 

Featured Reviews

Ankit  Shukla - PeerSpot reviewer
Mar 17, 2023
Options to connect with extendable sources in three buckets comes in handy
Our primary use case for Snowflake is inputting data generated by AWS This solution has helped our organization by being easy to maintain and having good technical support. The features I have found most valuable are the options to connect with extendable sources in three buckets in which we can…
SurjitChoudhury - PeerSpot reviewer
Feb 20, 2024
Offers seamless integration capabilities and performance optimization features, including extensive indexing and advanced tuning capabilities
We created and constructed the warehouse. We used multiple loading processes like MultiLoad, FastLoad, and Teradata Pump. But those are loading processes, and Teradata is a powerful tool because if we consider older technologies, its architecture with nodes, virtual processes, and nodes is a unique concept. Later, other technologies like Informatica also adopted the concept of nodes from Informatica PowerCenter version 7.x. Previously, it was a client-server architecture, but later, it changed to the nodes concept. Like, we can have the database available 24/7, 365 days. If one node fails, other nodes can take care of it. Informatica adopted all those concepts when it changed its architecture. Even Oracle databases have since adapted their architecture to them. However, this particular Teradata company initially started with its own different type of architecture, which major companies later adopted. It has grown now, but initially, whatever query we sent it would be mapped into a particular component. After that, it goes to the virtual processor and down to the disk, where the actual physical data is loaded. So, in between, there's a map, which acts like a data dictionary. It also holds information about each piece of data, where it's loaded, and on which particular virtual processor or node the data resides. Because Teradata comes with a four-node architecture, or however many nodes we choose, the cost is determined by that initially. So, what type of data does each and every node hold? It's a shared-no architecture. So, whatever task is given to a virtual processor it will be processed. If there's a failure, then it will be taken care of by another virtual processor. Moreover, this solution has impacted the query time and data performance. In Teradata, there's a lot of joining, partitioning, and indexing of records. There are primary and secondary indexes, hash indexing, and other indexing processes. To improve query performance, we first analyze the query and tune it. If a join needs a secondary index, which plays a major role in filtering records, we might reconstruct that particular table with the secondary index. This tuning involves partitioning and indexing. We use these tools and technologies to fine-tune performance. When it comes to integration, tools like Informatica seamlessly connect with Teradata. We ensure the Teradata database is configured correctly in Informatica, including the proper hostname and properties for the load process. We didn't find any major complexity or issues with integration. But, these technologies are quite old now. With newer big data technologies, we've worked with a four-layer architecture, pulling data from Hadoop Lake to Teradata. We configure Teradata with the appropriate hostname and credentials, and use BTEQ queries to load data. Previously, we converted the data warehouse to a CLD model as per Teradata's standardized procedures, moving from an ETL to an EMT process. This allowed us to perform gap analysis on missing entities based on the model and retrieve them from the source system again. We found Teradata integration straightforward and compatible with other tools.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"A user-friendly and reliable solution."
"Very easy to use and easy to query."
"It is quite easy to manage."
"The initial setup is very simple."
"The querying speed is fast."
"The most valuable feature has been the Snowflake data sharing and dynamic data masking."
"This is the advanced version of the cloud version, so it's really a flexible tool. If you have it implemented at home, you can access it from anywhere."
"The most valuable features of Snowflake are that you have to pay per usage, and you don't have to worry about the maintenance of the data warehouse because it is on the cloud."
"Teradata's most valuable feature is that it's easy to use."
"When it comes to integration, tools like Informatica seamlessly connect with Teradata. We ensure the Teradata database is configured correctly in Informatica, including the proper hostname and properties for the load process. We didn't find any major complexity or issues with integration."
"The two types of partitioning have been very significant for us - row and columnar partitioning."
"It handles large amounts of information with a linear performance increase, in relation to a HW investment."
"It's very, very fast"
"Cuts time to process huge amounts of data with efficient analytical queries."
"Teradata features high productivity and reliability because it has several redundancy options, so the system is always up and running."
"It has a solid set of tools and consulting services."
 

Cons

"We would like to be able to do modeling with Snowflake. It should support statistical modeling."
"An additional feature I'd like to see is called materialized views, which can speed up some run times. I'd like it to be able to be used where you can have multiple tables inside them; materialized view. That would be nice. As well as being able to run cursors, to be able to do some bulk updates and some more advanced querying, table building on the fly."
"There is a scope for improvement. They don't currently support integration with some of the Azure and AWS native services. It would be good if they can enhance their product to integrate with these services."
"The solution needs more connectors."
"They don't have any SLAs in place. It would be better if they did."
"There are three things that came to my notice. I am not very sure whether they have already done it. The first one is very specific to the virtual data warehouse. Snowflake might want to offer industry-specific models for the data warehouse. Snowflake is a very strong product with credit. For a typical retail industry, such as the pharma industry, if it can get into the functional space as well, it will be a big shot in their arm. The second thing is related to the migration from other data warehouses to Snowflake. They can make the migration a little bit more seamless and easy. It should be compatible, well-structured, and well-governed. Many enterprises have huge impetus and urgency to move to Snowflake from their existing data warehouse, so, naturally, this is an area that is critical. The third thing is related to the capability of dealing with relational and dimensional structures. It is not that friendly with relational structures. Snowflake is more friendly with the dimensional structure or the data masks, which is characteristic of a Kimball model. It is very difficult to be savvy and friendly with both structures because these structures are different and address different kinds of needs. One is manipulation-heavy, and the other one is read-heavy or analysis-heavy. One is for heavy or frequent changes and amendments, and the other one is for frequent reads. One is flat, and the other one is distributed. There are fundamental differences between these two structures. If I were to consider Snowflake as a silver bullet, it should be equally savvy on both ends, which I don't think is the case. Maybe the product has grown and scaled up from where it was."
"There is a need for improvements in the documentation, this would allow more people to switch over to this solution."
"The solution should offer an on-premises version also. We have some requirements where we would prefer to use it as a template."
"The scalability could be better. The on-premises solution is always more complicated to scale."
"The cloud is the new challenge and the new opportunity."
"There is some improvement required on OLTP level and some analytical function is missing."
"The solution needs improvement in its stability, support and pricing."
"Teradata's pricing is quite high compared to Redshift, Synapse, or GCP alternatives."
"​I think the UI is not there yet. It could be improved by being more user-friendly.​"
"Teradata is an expensive tool. Like, if you're already using Microsoft products like Windows, they'll market all their products together. And with the rise of cloud technologies, companies will adopt solutions that offer them some privileges or facilities. Similar to how SAP does it in the market, so do Microsoft and other companies. Even Oracle and other such tools are quite commonly seen compared to Teradata's competitors in everyday solutions."
"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."
 

Pricing and Cost Advice

"It is hard to say because we're usually engaged in the transition as opposed to the long term. Their storage costs are easily within pennies of what AWS S3 would normally cost. Most of the clients I've been working with are in the financial sector, and they're relatively small. I would put them in an SMB connection. The first thing we have to bring up for people is that they're going to build this. They shouldn't store their data in S3. They should pipeline directly into Snowflake and use it on their storage. So, the cost is a big issue because these are small to medium size companies, and that is the biggest thing we had to price point for them."
"The price of Snowflake is quite reasonable."
"It's expensive."
"Its price should be improved. It should be cheaper than Microsoft."
"Snowflake is cost-effective."
"Snowflake is a cost-effective solution."
"They give a different price for every single company. I don't know if I negotiated that well, but we got the enterprise tier for $3 a credit, and the other two were a dollar-ninety a credit. I suspect we don't have almost zero compute usage, but I know that our annual contract packages are below all of their minimums."
"Part of the problem with the pricing is that it is very difficult for businesses to get an idea of how expensive it might be until they actually start using Snowflake."
"The cost of running Teradata is quite high, but you get a good return on investment."
"Teradata is a very expensive solution."
"Teradata is expensive, so it's typically marketed to big customers. However, there have been some changes, and Teradata is now offering more flexible pricing models and equipment leasing. They've added pay-as-you-go and cloud models, so it's changing, but Teradata is generally known as an expensive high-end product."
"The price of Teradata is expensive. However, what they deliver they are outstanding. If you're looking for an inexpensive solution to run a database, this isn't your tool. It's the Ferrari of databases for data warehousing."
"I am using the free version of Teradata."
"The price needs to be more competitive as Hadoop, Redshift, Snowflake, etc are constantly making way into EDW space."
"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."
"The price of Teradata could be less expensive."
report
Use our free recommendation engine to learn which Data Warehouse solutions are best for your needs.
787,061 professionals have used our research since 2012.
 

Comparison Review

it_user232068 - PeerSpot reviewer
Aug 5, 2015
Netezza vs. Teradata
Original published at https://www.linkedin.com/pulse/should-i-choose-net Two leading Massively Parallel Processing (MPP) architectures for Data Warehousing (DW) are IBM PureData System for Analytics (formerly Netezza) and Teradata. I thought talking about the similarities and differences…
 

Top Industries

By visitors reading reviews
Educational Organization
27%
Financial Services Firm
13%
Computer Software Company
10%
Manufacturing Company
6%
Financial Services Firm
25%
Computer Software Company
10%
Manufacturing Company
8%
Healthcare Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about Snowflake?
The best thing about Snowflake is its flexibility in changing warehouse sizes or computational power.
What is your experience regarding pricing and costs for Snowflake?
The tool's pricing is based on the number of queries you want on your database. The cost is small. To get the tool's pricing, you can do the math based on the cost per query, which is $0.002. If yo...
What needs improvement with Snowflake?
I can only access Snowflake from the web. It would be better if we could have an app that we can install locally on our laptops to connect to the server without needing to go to the web page. Apart...
Comparing Teradata and Oracle Database, which product do you think is better and why?
I have spoken to my colleagues about this comparison and in our collective opinion, the reason why some people may declare Teradata better than Oracle is the pricing. Both solutions are quite simi...
Which companies use Teradata and who is it most suitable for?
Before my organization implemented this solution, we researched which big brands were using Teradata, so we knew if it would be compatible with our field. According to the product's site, the comp...
Is Teradata a difficult solution to work with?
Teradata is not a difficult product to work with, especially since they offer you technical support at all levels if you just ask. There are some features that may cause difficulties - for example,...
 

Comparisons

 

Also Known As

Snowflake Computing
No data available
 

Overview

 

Sample Customers

Accordant Media, Adobe, Kixeye Inc., Revana, SOASTA, White Ops
Netflix
Find out what your peers are saying about Snowflake vs. Teradata and other solutions. Updated: May 2024.
787,061 professionals have used our research since 2012.