Snowflake Reviews

Snowflake is used for data warehousing.

The most valuable features of Snowflake are its performance and power.

Snowflake could improve if they had an Operational Data Store(ODS) space.

I have been using Snowflake for approximately four years.

The stability of Snowflake is good.

The scalability of Snowflake is very good.

I have approximately six customers using this solution but in addition, I am directing more.

The technical support from Snowflake was poor previously, they have improved significantly.

Snowflake has an easy setup and it is quick.

There is a license needed to use this solution. There are a few licensing options available. They have a pay-as-you-go option, but it is recommended to pay upfront.

I would recommend this solution to others.

I rate Snowflake a nine out of ten.

We are also using Apigee we have various consumption patterns, data enrichment, and few shedding of the data, and everything goes into Snowflake. If it is multiple consumers, it goes into AMQ, Kafka, or multiple streams to consume. There are specific APIs that we offer after we send the data into the S3 bucket. We have Apigee APIs for consumption, and there are three to four different patterns. For example, we enrich the data, flatten it, and structure everything before the customers going to go into Snowflake. 

There are going to be specific clients who need specific data from the overall data lake, those are going to be exposed as APIs. We have multiple customers needing the same data and for this, we move them into the streaming Kafka.

Apigee does not communicate directly with Snowflake. We have data registration, and everything is coming into something that is called the trusted bucket. The  Apigee interface API is written off the S3 bucket. The S3 bucket data is moved into the Delta Lake, and where the data are stored from the Delta Lake, it sends it to Snowflake. We have Apigee going to Delta Lake and S3 bucket, but  Apigee does not go to Snowflake, these are two areas where it goes to. 

We have Kafka consuming directly off Delta Lake, and it sends data to Kafka through the AMQ. We have its setup, and we have interfaces that come directly to Snowflake to pull the data. It is then flattened and enriched, and it is used for many purposes, such as reporting.

Snowflake's most valuable features are data enrichment and flattening.

I have used Snowflake within the last 12 months.

The complexity of the initial setup of Snowflake depends on the use case. However, Snowflake itself, we don't set it up. The difficulty comes from the ingestion patterns, depending on what data I'm putting in, what kind of enrichment, and what additional value we have to add. However, it does tend to get complex because we have a lot of semi-structured data which we need to handle in Snowflake. There have been some challenges.

Snowflake has multiple implementations. For example, it can be implemented on Amazon AWS and on-premise. The data between these two cannot work together because they have different time zones. That's where the integration can be difficult because it is similar to them being on separate islands, they are completely separate. At some point, everything is going to go into the Amazon AWS Snowflake, but right now there are two islands that are completely different. We have to pull the data out and send it out again separately through a different pipeline.

In the future, this type of implementation should be easier. The integration could be better. 

I rate Snowflake an eight out of ten.

The primary use case is data platforms, specifically data warehousing. It involves restoring and moving data within the platform to prepare it for analysis, routing activities, or serving as the backbone for applications. 

Snowflake also advertises different workstreams, but my customers mostly use it as their core platform to ingest data and serve the onward goals of the wider company.

The most valuable feature of Snowflake is consumption-based costs, which means that you only pay for the storage and compute you use. There's a complete separation of storage and computing, so you don't need to add another server to increase storage or computing. From a costing perspective, it's well-positioned. 

Snowflake's time travel is also incredibly useful, and they have a function called "UNDROP," where you can undo a table drop. Data sharing and replication for Snowflake are strong, and they have a data marketplace with public and private data sets available for sharing. Companies can put their data on the marketplace, and anyone can use it by starting the payment model. The data is provided live straight to you, and it appears as if it were just another database in your own environment.

The main thing I'm excited to see at some point with Snowflake, hopefully - I've not seen anything coming out of it yet - is Git integration into the worksheets and the UI. Sometimes it can be tricky to manage multiple environments if you're purely using Snowflake as your scripting and pipeline environment. This is handleable, so if you use third-party tools like DBT, Matillion, etc., those can help. But if you're looking purely within Snowflake itself, it'd be great to have some form of Git support.

For the future releases, I would love it if they one day decided to implement their own GUI-based transformation tool environment. I know that many competitors like Azure have to Sign Up, and Azure Data Factory can sit in. However, Azure is a very different beast that serves all sorts of different processes, and an argument could be made for whether it's the best to each of those or not. Specifically within Snowflake, I would love it if they could get some form of orchestration built-in for transformation that doesn't have to be controlled directly through code all the time.

I have been using Snowflake for five years. 

It is an incredibly stable solution. It will only go down if your cloud provider itself goes down. So, let's say your Snowflake is hosted in Azure London. If the Azure London data center goes down, I would only see Snowflake going down. If that does happen, Snowflake does have plenty of options for failback replication and rollover backups. 

So we have quite a few customers that, for example, need their data restored in AWS London, and they've got a backup or a replication stored in Azure London. If AWS London goes down, then Azure London one will kick in and become the primary account, and all of the URLs, etcetera, remain the same because they've set up failover URLs and connections for it. At least for the end customer, there's no change. It's only for the architecture and developers behind the scene who then have to double-check things and do all the normal due diligence. But it runs very smoothly

It is a highly scalable solution. There is no limit on storage or computing. They have everything on consumption-based pricing, but you can have what's known as a multi-cluster warehouse. So, warehouses are what you use for the compute.

The multi-cluster warehouses will sit there originally as a single cluster. But then, if there are enough concurrent queries taking place in that warehouse, it can, as it needs, just spin up another one from another one and another one to meet those current needs. And as soon as they can dive down again, it can switch those clusters off again one by one. And you can create as many clusters, warehouses, as many as you need. There is no scaling issue at all. I've seen it most, like, 10,000 queries a second, and it's run very, very smoothly.

The customer service and support team is very useful and strong. They've got support built directly into the Snowflake UI. So wherever you are on the platform, and you see an issue, you can click into the support area and submit your ticket, including direct things like the query ID that you're using or multiple query IDs and all that stuff. 

I find Snowflake to be very responsive, and if you submit a top-level ticket, you can get a response very quickly. The lowest tier of tickets might take 48 hours sometimes, but overall, they are very helpful.

I personally don't see any of the competing cloud platforms coming close right now to what Snowflake offers. An argument could be made with GCP and Datadog are getting closer. Also, a new AWS Redshift is on the horizon, like a whole new AWS Redshift 2.0. But right now, I've not seen anything that comes close. Snowflake, to my understanding, is the only platform that fully separates your storage and computing, essentially. And it's the only platform I've seen with things like time travel. It's got a whole bunch of great features that I don't know if other tools also have, but it supports semi-structured data. It supports automated tasks, alerts, and reporting. And the data sharing is a massive one. GCP now also has its own data-sharing potential, where you can share data with other GCP accounts. I've not used it myself, but to my knowledge, whilst they have the sharing, they don't have anything that even comes close to the Snowflake data marketplace that allows customers to sell or share their data outside the wider world. And it doesn't have anything that comes close to the kind of private equipment where customers might share their own data internally or to their own. And I think there was one more thing. 

Snowflake also have some really good support for Python, Scalar, and Java through what they call Snowpark, which was launched last year. But more recently, this year, it was announced they're really pushing forward with their StreamLINK integration. It will allow customers to host applications on Snowflake and share those applications with other users in a very similar kind of marketplace environment they use for data sharing. I don't think there's anything that any of the other competitors have right now.

The deployment model is delivered as a service. So the most deployment you have to do yourself is by deciding which cloud provider and region you want it to be hosted in. But Snowflake will actually host it themselves, so there's no deployment beyond clicking from a dropdown and clicking okay, and it'll magically appear.

Moreover, it's very easy to maintain because it's delivered entirely as a service. Snowflake takes care of all the patches, upgrades, maintenance, security tweaks, etc.

We have many long-term customers who have been using Snowflake for years, and they wouldn't continue to use it if they weren't seeing a strong return on investment.

There are many options for starting a Snowflake deployment, but I recommend working with a partner who can provide best practices and guidance. It could be through Snowflake directly or another service partner. Working with a partner can save you time and prevent mistakes down the road.

Overall, I would rate the solution a ten out of ten. 

We implement this solution for our customers. It is a cloud data warehouse. It is SaaS, and it can be run on Azure, AWS, or something else. We are using its latest version.

It is a very good platform. It can handle structured and semi-structured data, and it can be used for your data warehouse or data lake. It can load and deal with any data that you have. It can extract data from an on-premises database or a website and make it available in the cloud.

It has very fast implementation and integration as compared to other solutions. There is no need for the DBA to manage or do the day-to-day DBA tasks, which is one of the greatest things about it.

In future releases, it can also support full unstructured data.

We have been using this solution for a year.

It is stable.

It has very good scalability. Your data can grow in the platform. We have at least 50 users of this solution in an organization.

Their vendor is wonderful. I only have good words for them.

It is not too complex. Its implementation is easy even for those people who don't know Snowflake and are coming from other environments, such as Oracle or SQL Server.

It can be implemented very quickly. Our customers in Israel implemented it very quickly. It was much faster to implement than other platforms.

It is on a monthly basis. It is based on your usage. There are no additional costs from the point of the licensing fee.

We do give some kind of evaluation to the customers about how much it is going to be. You can decide in Snowflake the virtual machine that you are using for customers. There are several kinds of virtual machines that you can use. It is similar to the clothing sizes: small to extra large. If you need more power in the coming month, you can decide in advance and take a more powerful machine. You can just select it from the platform. You can also decide which machine you want to take for extracting data.

I would advise others to check themselves how fast its implementation can be and how responsive it is. I would also recommend evaluating it before choosing other solutions, such as Microsoft Synapse or Amazon Redshift. You can test it yourself by using a test case. You can try to load the data on each platform, which can take a few weeks, but you will get to know the advantages of this solution. It is very different from other solutions.

I would rate Snowflake a nine out of ten.

I mostly build or design data warehouse analytics solutions using Snowflake.

The productivity across the teams that use Snowflake I believe is higher than it would be without the solution.

Snowflake has three great features: Snowpiping is proving to be very valuable, Time Travel is excellent, and Snowpipes are another great functionality the solution has made available.

Snowflake needs transparency over costs and pricing.

I have been using the solution for three years.

I give the stability an eight out of ten. We rarely have issues.

I give the scalability an eight out of ten.

I have used many on-premise solutions in the past and also Azure Synapse Analytics.

The initial setup is straightforward. I give the setup an eight out of ten.

A basic implementation is quick and we only have to set up Snowflake and the cloud service. We need one engineer and one designer for the implementation.

Depending on the complexity of the implementation, we may need to use a third party or help from the vendor.

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. Until they start pushing large amounts of data through, we will not really know. I believe that it is very difficult for businesses to make a commitment.

I give the solution an eight out of ten.

My advice is to start Snowflake and not spend too much time thinking about how we could use the solution or what it could be used for. The key is just getting started.

Basically, if at all, we wanted to have an interface for data warehouses on the cloud which worked on Azure or AWS. Snowflake, provides a more intuitive, rapid user interface where people can connect and maintain warehouses and share data among the people in the companies easily. Its pricing model and the model have made maintaining virtual warehouses simpler.

I appreciate the Snowflake marketplace, where you can drop data and allow other people throughout the world to access it. You can go to the Snowflake marketplace and connect to some data. If somebody else publishes, for example, COVID-19 data or weather data, you can sign up for new data sets and bring them into your warehouse, which I found very interesting.

You can connect to different cloud sources, including Azure and AWS. 

You can report out, and all the cloud technologies have connected to Snowflake, allowing you to move the data or get the data into Snowflake. 

The initial setup was pretty simple. 

It scales really well. 

The solution is stable. 

The solution is reasonably priced. 

I don't know about GCP, if they have connected for GCP. If they don't, they should allow for it.

Overall, they're doing great. I don't have any specific complaints or improvements that need to happen.

I've used the solution for a couple of years now. 

The solution is quite stable since everything is in the cloud, and the data these days has become cheap with storage and everything in the cloud. Through clusters and warehouses, sizes can be increased or decreased based on usage, and they can be turned on and turned off. Sustainability-wise, I think it's a pretty good solution.

It is scalable. The warehouses or auto-scaling features in the warehouses are great. You can go from small to medium to large all the way up to extra large, and there are different auto-scaling tasks that can happen. You can turn it on and turn it off based on the usage or auto-turn it on and turn it off. That's a pretty nice feature to have and we find it both sustainable and scalable for sure.

I work for clients, so last time when I worked for a client, there was a group of 100 people who were actually signed up to use Snowflake. 

I've never dealt with technical support. We did have people from Snowflake working with us directly, and we never ran into any issues that needed troubleshooting. The personnel from Snowflake, of course, would resolve whatever came up. 

I come from an Azure background as well, so Microsoft also comes with Azure Synapse, where it's a similar functionality as Snowflake, where it's warehousing on the cloud. Azure Synapse is also good. I'm unaware of AWS or GCP, and I heard that Google Cloud Platform also has Big Query and big data capabilities, which are tough competitors for Snowflake and other cloud warehousing tools.

The implementation process was pretty straightforward. I didn't set it up, though. I used an already set up version. I just had to connect. I had to push data from Azure to Snowflake, create tables there, and have data loaded into those tables, and that's it. I wasn't doing anything else, so I didn't work on the infrastructure of Snowflake.

You would need a group of two or three people to maintain the product.

I work for a consulting firm, so I don't work for the client, so I really don't know what the company used for deployment.

Licensing was based on the warehouse. I don't recall it being very expensive. 

I'm a consultant and end-user.

I'm not currently using the solution right now and do not recall the last version I was on. 

Now, I'm working for a different client on a different platform altogether. My company, as such, doesn't use Snowflake since we are in consulting. We have expertise in something, and then we help the clients deliver that solution on the technology.

Potential new users should just definitely give it a shot. They should start off with a POC, proof of concept, for the data that they have, and then, if everything works well and they can migrate in a cost-effective way. 

I would recommend Snowflake to start off with since it's just picking up over the last couple of years. If I have to recommend anything, however, it would be more Microsoft tools I would recommend since that all comes as a package. You can do Synapse and Azure Data Factory, which is  for ETL. You can also do Azure Data Lake Storage. There are different things that you can do when you buy something in a package like that. That said, I definitely recommend Snowflake if someone wants to give it a shot.

I'd rate the solution eight out of ten. 

We work with multiple customers who were asking for this and other similar solutions. We've since had several team members certified in Snowflake and we have a certified team working with that solution and keeping up to date with developments. I'm the general manager of the company and we are implementers. 

Snowflake has its own features in comparison to other similar solutions like Exadata. This gives it huge competitive power. It has a very good interface tool with its own benefits and features which are really useful for our needs from a computation and storage perspective. I think this solution provides the best potential of any data warehousing product where they choose to use Snowflake instead of Oracle or DBII. The product can be leveraged with respect to better performance, auto tuning, competition and performance. From an architectural perspective, the solution has all the ingredients it requires. 

We've come to realize that for many customers, pricing of this solution is an issue. Maintaining Snowflake clusters is challenging and cost intensive. Reporting could also be improved. Any data that moves out of Snowflake is being cached. If I have 400 to 500 end users, with 100 or 200 reports on a daily basis, all the reports will be cached. It's a matter of ensuring that costs can be optimized. The combination of Red Warescape plus Snowflake is a combination from the design and development perspective. But the combination from the reporting perspective to micro strategy on top of Snowflake could be a better feature, so there's a combination that has to be considered.

I've been using this solution for about 10 months. 

Our customers tell us that it is a stable solution. 

We're working in 32 countries with enterprise size customers. We're still waiting to see what happens with that level of scalability and how the solution performs. If this product can be further fine-tuned or optimized in such a way that it becomes a very good fit for the Azure platform, that would be great. 

They provide very good documentation on implementation design and development perspectives. 

I think the initial setup is straightforward. Anyone who has worked on these types of solutions will pick it up quickly.

It really depends on the nature of the implementation. If it's a small or medium sized company, we focus more on the pricing. If that can be brought down, I think Snowflake has a high potential that it can meet and can create a big name for itself in the big data cloud implementation platform. It has all the features. It already has all the complementary features to deal with the challenges. Those are built in and taken care of. It could be on Google cloud, or it could be on Azure or it could be on Amazon.

I'll rate this solution a nine out of 10. 

I am using Snowflake for migrating data and table backups.

The most valuable feature of Snowflake is its performance. We can access the data quickly. Additionally, it handles structured and non-structured data.

The solution could improve by allowing non-structured data, such as PDFs, images, or videos. We cannot see the data.

I have been using Snowflake for approximately three years.

The stability of Snowflake is good.

Snowflake is a scalable solution.

We have approximately 200 to 300 people using the solution.

The initial setup of Snowflake is easy.

If the use case fits the solution then I would recommend it. For example, if you have large data and want the rational database backed up, this solution would be a good choice.

I rate Snowflake an eight out of ten.