We changed our name from IT Central Station: Here's why

Snowflake OverviewUNIXBusinessApplication

Snowflake is #1 ranked solution in top Data Warehouse tools and top Cloud Data Warehouse tools. PeerSpot users give Snowflake an average rating of 8 out of 10. Snowflake is most commonly compared to Microsoft Azure Synapse Analytics: Snowflake vs Microsoft Azure Synapse Analytics. Snowflake is popular among the large enterprise segment, accounting for 68% of users researching this solution on PeerSpot. The top industry researching this solution are professionals from a computer software company, accounting for 27% of all views.
What is Snowflake?

Snowflake provides a data warehouse built for the cloud, delivering a solution capable of solving problems for which legacy, on-premises and cloud data platforms were not designed.

Snowflake was previously known as Snowflake Computing.

Snowflake Buyer's Guide

Download the Snowflake Buyer's Guide including reviews and more. Updated: January 2022

Snowflake Customers

Accordant Media, Adobe, Kixeye Inc., Revana, SOASTA, White Ops

Snowflake Video

Archived Snowflake Reviews (more than two years old)

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
R&D Operations Manager at a manufacturing company with 1,001-5,000 employees
Real User
You can assign roles and responsibilities, limiting access to data
Pros and Cons
  • "I like the idea that you can assign roles and responsibilities, limiting access to data."
  • "If you go with one cloud provider, you can't switch."

What is our primary use case?

We are a big data company. We have many thousands of devices deployed from our customer base. These devices upload data, on an hourly basis, to a central storage. Next, we run some ETF processes that crunch and process data, then we store that data in a structured way on Snowflake.

Over the past six months, it has been more of a development project.

I am using the latest version.

What is most valuable?

  • I like the idea that you can assign roles and responsibilities, limiting access to data. That has been very interesting to us. 
  • The robustness of the system is very useful to us. 
  • The availability of the system. 

What needs improvement?

We would like Snowflake to be able to do inter-cloud migrations. That would be great. I want to be able to switch clouds.

For how long have I used the solution?

Six months.

What do I think about the stability of the solution?

It is stable.

What do I think about the scalability of the solution?

If you go with one cloud provider, you can't switch.

We have very few users. There is just a very limited number who are mostly developers. We did not roll out the end product. We did not roll out product and services based on that foundation/infrastructure yet.

How are customer service and technical support?

I have not personally contacted technical support.

Which solution did I use previously and why did I switch?

We previously used HPE and Microsoft Insight. We switched to Snowflake for the availability, security, and loading times.

How was the initial setup?

The initial setup was very straightforward. It was very quick. The complexity came from our specific use case scenario.

Which other solutions did I evaluate?

We also looked at HPE and Microsoft Insight.

What other advice do I have?

Analyze your user scenario. If your scenario is managing large amounts of data in extremely, different environments in a structured way, then this is a good option.

I would rate this solution as an eight (out of 10).

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Sr. Software Developer at Tech Mahindra Limited
Real User
Impressive performance from massively parallel processing, supports ELT for importing data, and has awesome technical support
Pros and Cons
  • "It has great flexibility whenever we are loading data and performs ELT (extract, load, transform) techniques instead of ETL."
  • "They do have a native connector to connect with integration tools for loading data, but it would be much better to have the functionality built-in."

What is our primary use case?

The primary use case for Snowflake is in our data warehouse project. We have a private DW and whoever has the credentials can access it. I am a data integration developer and we are using ETL tools to extract the data from different source systems and then load it in the data warehouse.

What is most valuable?

Snowflake is the latest technology. It has great flexibility whenever we are loading data and performs ELT (extract, load, transform) techniques instead of ETL.

This solution automatically performs micro-partitioning when the data is loaded. This creates a dynamic partition and based on the cluster, the performance is fast and really impressive.

Snowflake is using MPP, massively parallel processing techniques, which is a great feature. It saves developers time and allows us to focus more on client requirements.

What needs improvement?

It is difficult in some cases to perform ETL and this is something that should be included. As it is now, I use Informatica PowerCenter to load data from on-premises to the Snowflake cloud-based data warehouse. If this could be done by Snowflake directly, without an external integration tool, then it would become a full package. It would be awesome.

They do have a native connector to connect with integration tools for loading data, but it would be much better to have the functionality built-in. We would like to be able to just write an SQL query and do our work.

For how long have I used the solution?

I have been working with Snowflake for six months.

What do I think about the stability of the solution?

We have not had any major issues with stability.

What do I think about the scalability of the solution?

Snowflake does not require manual scaling because it does it for you. Developers just need to load the data and process the query. That's it. The developer's job is not to spend time improving performance, as it was with an on-premises solution. We had to do the partitioning, collect the stats, and everything else. In the case of this cloud-based solution, it doesn't require as much work. Instead, we can focus on the queries.

We are planning to increase our usage of Snowflake.

How are customer service and technical support?

I have been in contact with technical support many times and it was awesome. I got great support. Whenever I needed anything they were ready to help me out, which was nice.

Which solution did I use previously and why did I switch?

I have experience with Informatica PowerCenter and Oracle. PowerCenter uses ETL techniques instead of ELT. Oracle does not automatically perform micro-partitioning. Instead, you have to partition manually and it is a static partition.

Prior to Snowflake, I was using an on-premises data warehouse. Snowflake is the first experience I have had with a cloud-based data warehouse. It is an awesome tool.

How was the initial setup?

There is no need to install this software, which is the best part. It doesn't require any maintenance, and although DBA support is required, it is much less compared to an on-premises solution. This type of cloud-based solution has no requirement for software, hardware, or maintenance because everything is managed by Snowflake's system.

What about the implementation team?

The only assistance I had during the setup was from the integration tool, Informatica PowerCenter. This was used to export our on-premises data from Oracle and import it to Snowflake on the cloud.

What's my experience with pricing, setup cost, and licensing?

You pay based on the data that you are storing in the data warehouse and there are no maintenance costs.

What other advice do I have?

This is an awesome tool, but there is room for improvement in terms of integration. Also, in terms of management, nothing is perfect and everything can be improved.

I would rate this solution an eight out of ten.

Which deployment model are you using for this solution?

Private Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Learn what your peers think about Snowflake. Get advice and tips from experienced pros sharing their opinions. Updated: January 2022.
564,643 professionals have used our research since 2012.
Vice President of Business Intelligence and Data Engineering at a comms service provider with 201-500 employees
Real User
Top 20
Fast, convenient and requires almost no administration
Pros and Cons
  • "The thing I find most valuable is that scalability, space storage, and computing power is separate. When you scale up, it is live from one second to the next — constantly available as you scale — so there is no downtime or interruption of services."
  • "Maybe there could be some more connectors to other systems, but this is what they are constantly developing anyway."

What is our primary use case?

We needed a data warehouse and we made a decision on what is the right tool for us as a data warehousing tool by comparing products. We looked into Microsoft Azure, Red Shift and Snowflake. In the end, we decided on Snowflake because it looks more up to date, it seemed much better purposed as a data cloud solution.

It was developed from scratch and dedicated to being used on the cloud and that was what we were looking for. It was not just an on-premises system which was then converted to use on the cloud. It was completely developed from scratch and purely focus on the cloud.

Because it was programmed with that dedication, it has some significant advantages.

What is most valuable?

The thing I find most valuable is that scalability, space storage, and computing power is separate. When you scale up, it is live from one second to the next — constantly available as you scale — so there is no downtime or interruption of services.

It has something like a time machine, as it is from Apple it incorporates that feature in a way similar to their operating system. So whenever you need a version of the data to test with, you can just go back and take a copy of what was backed up yesterday. It makes some things very easy. It backs up your data warehouses, so for example in our case, a colleague deleted a complete database and we just need to do an undrop on the database and the data was there again.

This helps you to have a development environment with current data. You can just clone your production environment and you have a development environment. Everything you do you can test it on real production data without destroying the production data itself.

These are significant advantages.

What needs improvement?

The company is constantly working to improve the product. Now they have a focus on data sharing, which is really great. We already share data with others who do not have Snowflake. That alone is already great. But if the other counterparts also have Snowflake, then it is extremely easy to share data. You can control access at low levels and even on the cell level. It is very secure.

With the improvements they continue to make, there is nothing now that I would say I miss or features that need to be added. Maybe there could be some more connectors to other systems, but this is what they are constantly developing anyway.

For how long have I used the solution?

We have been using this product for two years.

What do I think about the stability of the solution?

The product is very stable. We never had an issue with stability. It is reliable and it is extremely fast. For example, we had a stock procedure that took half an hour to complete on our SQL cluster, and in Snowflake it was running in two minutes. So that is a significant time savings for just one task.

What do I think about the scalability of the solution?

The number of people at our company currently using the solution depends on what we are trying to accomplish. We have four developers in Snowflake and then we also have users who are leaving data with us for our further analysis. That may be around ten other users.

With the growing data set we have and the increase in the size of our business, we will increase the use of Snowflake, but not with respect to the number of users. We are a small company and all the users who need to use it are already using it. We have more data that we need to load and which we want to integrate before we will make more usage of Snowflake.

How are customer service and technical support?

There is nothing for us to complain about when it comes to technical support. The response time is really great. Whenever we have an issue there is some delay because they are in San Francisco in the United States so there is a time difference. But when we raise an issue, we get answers immediately. We may not get the solution immediately, as that is not always possible. But we get some type of immediate response and days later we have a solution. The tech support is quite responsive.

Which solution did I use previously and why did I switch?

We use several products together for our framework. We have our data warehouse which is in Snowflake, we use Domo for standard reporting and we use R for data science analysis.

Before we had Snowflake we had a different solution. We switched to Snowflake because we felt the need to modernize our data warehouse architecture. We were also thinking about having other solutions in the cloud to reduce administration costs. With no effort on our part, we could have a stronger system compared to the effort and cost of doing a similar thing on-premises. This was the biggest advantage of Snowflake. We really do not need to have those administrative efforts anymore. Now we don't take care about when we run out of storage or that we need to buy better CPUs because if we need more computing power, we don't worry about it, we just use it and it is there.

How was the initial setup?

The setup for the product was straightforward. For us, it was a little bit of a challenge because when we implemented the data warehouse, we also changed the architectural concept and we implemented a better framework. Because this framework was new to us it complicated our installation. But Snowflake itself, if you want to use and you have a data warehouse already in place with the right framework, then it is straightforward. You just store your data in and that's it. What you use on top is material for orchestrating all the load jobs. But this is other integrations and other choices that are really outside Snowflake itself.

The initial deployment from purchase until it was up and running in production took two months.

What about the implementation team?

We had a consulting company help us for the initial two months of the setup and then afterward we did everything by ourselves. We were quite satisfied working with the consultants and they helped us to implement quickly. We mainly needed them because we implemented this metadata framework. In the beginning, we had this consultancy for analyzing our platform, which to select and which tools should be used. After we completed this initial portion of the project over the two months, we needed them mainly for completing the implementation of the metadata framework.

Snowflake itself is easy to learn. If you know SQL it is really not very hard. Everything is well documented and it is not a problem.

What's my experience with pricing, setup cost, and licensing?

The whole licensing system is based on credit points. That means you commit to using it and you pay for what you use. You can also make a license agreement with the company so that you buy credit points and then you use them. So if you buy credit points that you think will last you for a year, you pay a certain amount of money and then you have these credit points available. What you do not use in one year can be carried over to the next year and it is that easy. The advantage of buying more is that you get a discount when you buy a bigger package with more credits.

What other advice do I have?

There is not really much advice I can give people considering this solution except that they should use it and enjoy it. It really sounds simple but that is it. Of course, you need to be careful with the usage of your credit points. Because there are so many possibilities in configuring the way you build your data warehouse or infrastructure, the data warehouse might seem logical, but it is not the best with respect to using credit points. You need to be careful about this. It probably takes half-a-year experience and then you will know how to do it. If you don't know what you are doing, Snowflake also helps to optimize your usage so that you do don't use too many credits points. After one year, we realized we had spent a huge number of credit points and we talked to Snowfake and then they came to us and we analyzed our systems together and we optimized the usage.

On a scale from one to ten where ten is the best, I would rate Snowflake as at least nine. Why not a ten is only because maybe there is something better on the market which is a ten that I don't know about. For me, it is already a ten.

Which deployment model are you using for this solution?

Private Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Amazon Web Services (AWS)
Disclosure: I am a real user, and this review is based on my own experience and opinions.
it_user865563
Data Engineer at Celebal Technologies
Real User
Easy to scale, a simple initial setup, and good stability
Pros and Cons
  • "The initial setup is straightforward. You just need to follow the documentation."
  • "The solution could improve the user interface and add functionality to the system."

How has it helped my organization?

We mainly used SQL scripts and provided a solution for different owners who want to query a database but have several tables. Typically, it is not an easy task to read several tables, so we provided our client with a very crisp data model where they can get results in a very quick manner. We implemented distribution as well as weekly partitioning. 

What is most valuable?

The relational piece and how one dimension relates to another just by using a key is the solution's most valuable aspect. We are managing everything by using simple relations. It's all about the relationships between dimensions.

What needs improvement?

Right now, we need to write code, but if they could create a version of Snowflake that was more drag and drop for those managers that don't know how to code, it would be great for our business.

The solution could improve the user interface and add functionality to the system.

For how long have I used the solution?

I've used the solution for two years.

What do I think about the stability of the solution?

The solution is stable. We bring in incremental loads into Snowflake. There are pipelines that daily seed data from Oracle to a data warehouse. It's a prebuilt code and it allows for great stability.

What do I think about the scalability of the solution?

It's very easy to scale because Azure cloud's own data warehouse gives us that capabilities to scale up or down at any time we want. There are a great number of users on the solution, but it differs from client to client. One client, for example, has about 30,000 users.

How are customer service and technical support?

We've never been in touch with technical support.

How was the initial setup?

The initial setup is straightforward. You just need to follow the documentation.

What about the implementation team?

We handled the implementation ourselves. I've handled two or three projects previously, so I'm comfortable with the solution. We don't need assistance because we handle the consulting part.

What other advice do I have?

The solution is deployed on the cloud using Azure, where there's a data warehouse. We primarily use SQL scripts.

For those considering implementing, I'd advise that they understand the business very deeply first. Not every business would have a demand for Snowflake, so it's not for everyone. It's important to understand the requirements and then, if it makes sense, to implement Snowflake.

I'd rate the solution eight out of ten. I'd rate it higher if it had a better user interface.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Data & Analytics Practitioner at a tech services company with 1,001-5,000 employees
Real User
Could use better integration, but very stable with an easy initial setup
Pros and Cons
  • "They separate compute and storage. You can scale storage independently of the computer, or you can scale computing independently of storage. If you need to buy more computer parts you can add new virtual warehouses in Snowflake. Similarly, if you need more storage, you take more storage. It's most scalable in the database essentially; typically you don't have this scalability independence on-premises."
  • "The solution should offer an on-premises version also. We have some requirements where we would prefer to use it as a template."

What is our primary use case?

We primarily use the solution for data warehousing.

What is most valuable?

The entire managed service operations for the solution is great. Snowflake does everything for us. Whatever version they have, they implement the latest for us; we don't have to worry about any versions, any upgrades, anything else because they handle it.

What needs improvement?

The solution should offer an on-premises version also. We have some requirements where we would prefer to use it as a template. 

The integration capabilities could be improved.

For how long have I used the solution?

I've been using the solution for six months.

What do I think about the stability of the solution?

The solution has been very stable for us.

What do I think about the scalability of the solution?

We have not tested scalability, but the solution claims that it's scalable. It's on the cloud, so I imagine you could scale rather easily if you needed to. 

They separate compute and storage. You can scale storage independently of the computer, or you can scale computing independently of storage. If you need to buy more computer parts you can add new virtual warehouses in Snowflake. Similarly, if you need more storage, you take more storage. It's most scalable in the database essentially; typically you don't have this scalability independence on-premises. 

We have about 40 people using the solution. They're mostly business users.

How are customer service and technical support?

Technical support is good. Occasionally, they take a bit of time to resolve issues, but other than that they are okay. We're mostly satisfied with them.

Which solution did I use previously and why did I switch?

We're system integrators, so we use different solutions including SQL Server Data Warehouse and Greenplum as well as Snowflake at the moment.

I've used many data warehouse solutions, including Hadoop, and Oracle SQL Server Data warehouses. I switched from those to Snowflake because Snowflake is on the cloud and gives you separate computing and storage scalability, which Hadoop is unable to offer.

How was the initial setup?

The initial setup is straightforward. There's no deployment; it's just your code solution that needs to get up and running. You have a deal with Snowflake in terms of what environment you want, and when you want to use it, and they'll set it up within a day for you.

What about the implementation team?

Snowflake helped us with the implementation.

What other advice do I have?

We are system integrators, so for all our customers, we offer different solutions.

We only use the cloud deployment model. Snowflake doesn't offer on-premises deployments.

Snowflake on cloud is the best right now. There are only a few other options. Redshift is not scalable. With SQL Data Warehouse the concurrency is an issue, as well as scalability. Also, it does not have all the features that you see in an on-premises SQL Server.

Snowflake a good database. I'd recommend the solution to others.

I'd rate the solution seven out of ten. We are still new to the solution. There are a few things we still have to explore before we would give it 10. Typically, I come from a Hadoop background, so compared to Hadoop I think everything looks good before the data warehouse side. We're quite pleased with Snowflake and moving from Hadoop into Snowflake has been a very good transformation.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Cesar AugustoSiado Leyva
Business Intelligence Consultant at a tech services company with 201-500 employees
Consultant
A flexible solution with good clustering, and the pay-per-use feature is useful
Pros and Cons
  • "The most valuable features are the clustering, LS50, being able to change the size, the pay per use feature, the flexibility with many different sources and analytic applications."
  • "Support needs improvement, as it can take several days before you get some initial support."

What is our primary use case?

We are an IT Analytic Consulting company and we work with many different products. We have Snowflake and a Snowflake account mainly for education purposes and our internal training.

We connected it to different sources, mainly internal sources. Most of them are on-premises and some are on the cloud.

The deployment model is public.

What is most valuable?

The most valuable features are: 

The multi-clustering: being able to access stored data without contention.

Virtual Warehouse (VW) sizing: Change the size of your VW on demand. 

Zero copy clone: Easy to create development and test environments.

What needs improvement?

I would like to have a tool where you can easily see the price because they need clarity of pricing.

Support needs improvement, as it can take several days before you get some initial support.

Integration could be the key to provide an optimal solution.

In the near future, I would like to see a built-in basic analytics solution that can be embedded for testing purposes, so you can see data not only in tables but also in a graphical way in order to better prepare data for analytics.

Embedded analytics would be nice.

For how long have I used the solution?

I have been using this solution for four months.

What do I think about the stability of the solution?

The scenarios that we are using are not complex. For what we are using it's pretty stable.

What do I think about the scalability of the solution?

With a different cloud that warehouses are the standard for now but the scalability is pretty straightforward.

How are customer service and technical support?

In terms of support, it can take some time as there are not many people to provide support. Compared to other more stable providers it's a bit slower.

You have to wait several days to get support.

Which solution did I use previously and why did I switch?

Snowflake is not the only solution we are working with but it is the only solution that we are heavily focusing on and investing our efforts into the knowledge and the training.

How was the initial setup?

The initial setup can be complex at the beginning but once you get into it, it can be straightforward.

When you come from an on-premises solution and you have to change or shift to the cloud, it works very differently. Once you know the differences then it is straightforward.

What about the implementation team?

We did not implement this solution through a vendor, we did it ourselves.

What's my experience with pricing, setup cost, and licensing?

Pricing can be confusing for customers. For example, if a customer is asking for an estimate of the price, it's hard to tell because it is not easy to measure.

Improvement on the pricing and how it is presented is needed.

What other advice do I have?

I would suggest being careful with selecting resources. Each customer case can be completely different and each can require different resources.

It's not only the database itself but also how you integrate it with the analytics and the resources. The estimation of the resources is something that you have to pay a lot of attention to when selecting the resources because sometimes you will need EPL or ELT integration, which requires a tool, as does analytics.

For an end to end solution, you have to include other products.

I would rate this solution an eight out of ten.

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner.
Valai Gunapalan
Architect at Sony Corporation of America
Real User
Stable with good technical support, but the solution is expensive on longrun
Pros and Cons
  • "As long as you don't need to worry about the storage or cost, this solution would be one of the best ones on the market for scalability purposes."
  • "There are some stored procedures that we've had trouble with. The solution also needs to fine-tune the connectors to be able to connect into the system source."

What is our primary use case?

Our aim was to migrate everything from on-premise, so we just migrated as it is and then we had issues. Some use cases that were running on-premises were not installed. We just went through each case and then finalized the issues with some of the packages that were not working or some users that were not getting what they were expecting. We did deep analysis on each and every case and then looked for options in Snowflake and are now working with the team to move everything over to Snowflake

What is most valuable?

The data warehouse is one of the great concepts of Snowflake. The coding plans are also a great feature. You can switch out the values or sizes. 

What needs improvement?

It would be helpful if implementation could be handled more on the user-side. We need to train the users on best practices and how to use the solution properly. It's a cost issue. If they don't run it properly then it'll end up costing more money.

There are some stored procedures that we've had trouble with. The solution also needs to fine-tune the connectors to be able to connect into the system source.

For how long have I used the solution?

I've been using the solution for one year.

What do I think about the stability of the solution?

The solution is stable. We had only one failure, but that was because of AWS issues. Beyond that, I haven't seen anything else. From the Snowflake side, within 10 minutes they reported the AWS issue. It was under two hours of downtime because of the quick response.

What do I think about the scalability of the solution?

As long as you don't need to worry about storage or cost, this solution would be one of the best ones on the market for scalability purposes. We've migrated about 400-450 dealers onto the solution so far. We do intend to expand usage so there will be more users and more data. The drawbacks we've had with on-premises was space being a constraint and the user code having limitations.

How are customer service and technical support?

Customer support is good. There is always someone who's going to respond. They will let you know what can be done and what is possible.

How was the initial setup?

We did some testing and some comparisons, but it's all set up now and running fine. The deployment took about three months. Since we didn't want to disrupt the on-premises, or overload the system, we did most of the migrations on the weekend.

For maintenance, in the beginning, until you are through with training and performance tuning, you will need more people. You might need to start with seven or so, and then, for ongoing work, probably one or two people can manage it. 

What about the implementation team?

We had a Snowflake consultant on-site that assisted us with the implementation.

What's my experience with pricing, setup cost, and licensing?

It's an expensive solution. We can't predict exactly how much until we've streamlined everything and the user requirements have been completed, but normally they charge on the storage, which depends upon the average storage amount used for the month.

Which other solutions did I evaluate?

We looked at IBM because it also has on-premise solutions. We also looked at Azure as well as AWS.

What other advice do I have?

Because most of the issues you come across can be dealt with on the user's sites, it's important to educate the users and understand their requirements.

The best advice I can give is to understand the product and to try to stick to what is required. From the business side, you need to monitor usage and monitor the space because of on-premises constraints. If it gets filled up then you will have to react. However, this solution is very scalable. 

I would rate this solution between seven and eight out of ten. The solution still has some constraints that need to be addressed.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Data Sleek
Owner at a consultancy with 1-10 employees
User
Top 5Leaderboard
A true elastic data warehouse where you can scale computing by just issuing a SQL query

What is our primary use case?

We use Snowflake for our data warehouse. Amazing product. Redshift cannot compete with a true elastic data warehouse where you can scale computing by just issuing a SQL query (increase computer power) and resizing it down or putting computing unit to sleep. 

Snowflake has many more features:

When combined with Alooma, it's the best data integration system. No need for Talend and all these cumbersome tools.

How has it helped my organization?

We were able to implement the entire data eco-system in less than five months, from data integration, data warehousing, ELT, producing fact and dimensional tables, and finally reports.

What is most valuable?

  • Computing unit is accessible via SQL: being able to turn them on or off as needed.
  • Snowpipe (ingesting data)
  • Looking back in time (being able to look at data in the past within a query)
  • No data warehouse management
  • Support for JSON.

The list is pretty long.

What needs improvement?

  • Snowpipe auto-ingest should be automatic.
  • A better client UI or command line tool: I think SnowSQL is a little awkward.

For how long have I used the solution?

Less than one year.

What do I think about the stability of the solution?

Excellent.

What do I think about the scalability of the solution?

Excellent.

Which solution did I use previously and why did I switch?

Used it at a previous company.

How was the initial setup?

Yes. No hardware or server config is needed. Just create a user account.

What about the implementation team?

In-house.

What was our ROI?

Very good.

What's my experience with pricing, setup cost, and licensing?

Snowflake computing is very affordable. Less expensive than Redshift.

Which other solutions did I evaluate?

Yes. I looked at Redshift and Vertica.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Padmanesh NC
Big Data Solution Architect - Spatial Data Specialist at Sciera, Inc.
Real User
Top 5
The distributed architecture of Snowflake has the capacity to process huge datasets faster and allows us to scale up and down according to our needs
Pros and Cons
  • "The distributed architecture of Snowflake has the capacity to process huge datasets faster and allows us to scale up and down according to our needs."
  • "Snowflake has to improve their spatial parts since it doesn't have much in terms of geo-spatial queries."

How has it helped my organization?

We were using MySQL and MongoDB for our regular operations but when we grew, we were forced to handle a huge number of datasets. We could have petabytes of data in and out on a regular basis. We struggled a lot to complete the operations in a timely manner. With Amazon Redshift, we gained a lot in terms of timing, as well as project completion. Even-through we are happy with Redshift, in terms of pricing and availability of nodes, I am more comfortable with Snowflake. Some of the scoring mechanism really works well in the distributed architecture of Snowflake.

What is most valuable?

  • Scalability. This solution has the ability to load a huge number of datasets (I have experience with petabytes of data) and process them. Storage is not limited, and we can increase what we want.
  • Performance. The distributed architecture of Snowflake has the capacity to process huge datasets faster and allows us to scale up and down according to our needs.
  • Flexibility. This feature is helpful for the user to increase the node size and config depending on their need. There is no need to wait for hardware to be in place whenever we increase the dataset. Snowflake provides the option to increase the node or cluster size whenever required.
  • Multi-formatted accessibility. The Snowflake engine has the capability to read the following file formats: CSV, DELIMITER, FIXEDWIDTH, AVRO, JSON, BZIP2, GZIP, LZOP. The user can choose which format is best for their requirements.
  • Configuration. Even though its running in the AWS platform, it beats their platform product. I feel more flexible with this solution than I do with Redshift.
  • Snowpipe. Snowpipe is a better system to feed stream data to the Snowflake database.

What needs improvement?

Snowflake has to improve their spatial components since it doesn't have much in terms of geo-spatial queries.

For how long have I used the solution?

One to three years.

What do I think about the stability of the solution?

No

What do I think about the scalability of the solution?

No

How are customer service and technical support?

It's really good. I am happy with the product and the service.

Which solution did I use previously and why did I switch?

With Amazon Redshift, we gained a lot in terms of timing as well as project completion. Even through we are happy with Redshift, in terms of pricing and availability of nodes, I am more comfortable with Snowflake.

How was the initial setup?

The initial setup of Snowflake is very simple and straightforward. We do not need to read or understand any of the technical documentation. It is a plug-and-play service or platform.

What about the implementation team?

I have implemented this solution through an in-house team.

What was our ROI?

I can't directly convey ROI because we are not using only Snowflake. We are using multiple products to increase our revenue and decrease time consumption. This makes it difficult to calculate ROI.

Which other solutions did I evaluate?

I have experience working in Hadoop & Redshift as well. When I compare the three (Snowflake, Hadoop, and Redshift), Snowflake is more user-friendly in terms of configuration and maintenance.

Disclosure: I am a real user, and this review is based on my own experience and opinions.