Snowflake Reviews

Mostly, we use it for the data warehousing side of use cases, where you have, like, a huge amount of data, and you are required to do reporting in terms of data science, data warehousing, or ad hoc reporting. The use cases we have used are, for example, data coming from MedTech devices, mostly sensor data, which we need to load in Snowflake and do data analytics. We have been using the tool for a couple of MedTech clients.
 

The most important part of the tool is that computing and storage are totally separated, and it keeps on evolving every two weeks, with the tool having releases. New features are coming up in the tool. With respect to AI, the tool is also progressing well. The scalability and performance are quite good. If you have data, like in CSV or any other format, you can load it very quickly and then do your analysis. Columnar database performance, scalability, and the addition of new features are a few useful features of the tool.

I think people do not want to create pipelines for many customers now. Normally, we have this layer architecture, like layer one, layer two, layer three, or layer four, where we have raw data, integrations, business data, and then semantic data, so we have to create various pipelines. People don't have to create or maintain pipelines since, in the future, if there are any changes in the source data, it should be very easy to configure and create the pipeline rather than the developer doing that for them. Though it may not be possible to make improvements based on the expectations of the people, considering the AI market, code generation can be simplified a little bit by using streams. People want to be able to develop the pipeline without involving many developers by doing some configurations and creating the pipeline. The customer expectation is that they don't want to create tables for each report, but what happens currently is that if you don't create that, then you have to run the query every time. Suppose I have created raw data, and I want to do some aggregation. In that case, if I don't create a materialized view or a table, I have to run those aggregate queries again and again, which will cost me the cost attached to Snowflake usage. From an improvement perspective, Snowflake can evolve in terms of writing costly, expensive queries with less cost and try to see if pipeline development can be made a little easier.

I have been using Snowflake for a year and a half.

There were use cases where there were only 10 to 15 users. There was one requirement where the customer asked for 3,000 concurrent users to try to get a real-time report from the tool, but then our company suggested that Snowflake was not the right choice for them because it is more kind of a data warehouse, and they were looking more into transactional reporting. For Snowflake-based projects where we have worked, it is more concerning a smaller number of users, like around 20 users. However, if a huge number of users are required, Snowflake is not the right choice.

My company has partnered with Snowflake. Normally, we reach out to the account manager or regional manager, and sometimes we get support. Most of the time, we ask for support from the architecture and solutions part of it to review it or for some workarounds. Right now, we have not gone for low-level technical support from Snowflake. Whatever we have worked on, we are able to manage.

I have been working all my life on databases, so I have almost twenty five years of experience in databases starting from SQL, Oracle8i, Oracle 9i to MySQL, SQL Server and Redshift. I have also used Solr and Elasticsearch, which are not databases but all data-related things I have worked on, including PostgreSQL.

The main thing about Snowflake is that it is totally outside the customer's cloud. If I am an AWS customer, even if Snowflake is hosting on AWS, it is on a separate account right now. If somebody has some critical data that cannot be shared outside the cloud, then such customers or people are a little hesitant to use Snowflake. Recently, there were some breaches or password issues, so security concerns like that are there. There is also the costing part attached to the tool. Now, people are looking into tools that are available at a lower cost and offer more user-friendliness. The tool is a good data cloud product, but it is a little bit outside the customer's environment, which makes it difficult to convince the customer to use it.

Speaking about the product's initial setup phase, I would say that the product is used just from the cloud. We have not installed it in any environment. I work with the tool's SaaS version.

The tool does add some value to the company. When it comes to pipeline development work, though customers expect it to be faster, I think if you have simple files, you can load them in a day and analyze the data. Productivity-wise, it is definitely much better compared to Redshift. Redshift Spectrum is catching up with Snowflake, but I have not explored it. To be very frank, I am not very familiar with Azure Data Warehouse, so I am not sure how it is different from Snowflake, but from what I have seen, it has been good in terms of productivity.

The pricing part is based on the computing and storage. The costs are different and then there are services costs as well. I have heard that Snowflake is costlier than Redshift or GCP BigQuery. A small customer may not go for Snowflake.

Speaking of how Snowflake enhances our company's AI-driven projects or analytics, I would say that the tool has features like Document AI and Snowflake Cortex. AI can be used if the tool is for very basic use cases, like anomaly detection or prediction. With simple use cases, you don't have to set up a big infrastructure. You just load data and use the tool's services. I have not used the tool for complex AI projects. I am not an AI person. Rather, I can be described as a data engineer or data architect. In our use cases, we have explored the AI feature of Snowflake more from document processing and doing a simple exploration of the feature. For customers, I have not used Snowflake's AI feature.

Speaking about how Snowflake's scalability feature impacted our data processing and analytics tasks, I would say that the tool has a virtual warehouse, so it really helps. You can scale based on your needs. You can change the warehouse sizing, which will help with the scalability. You can just increase the warehouse size, and it gets your work done.

There are various ways to integrate the tool. I think the tool has connectors also, but the external table is one way to load your data in Snowflake and start analyzing it quickly. Now, the tool also works with Apache Iceberg format, though I have not explored that. With respect to Snowpipe, getting data from CSV to Snowpipe are things we use, and they are all quite easy to use. In terms of native connectors to various data sources, though I have not explored them, I see the tool has support for various connectors. I believe that will be good. For most of the use cases, data is loaded onto S3, and then we use Snowpipe along with external tables and Snowpark ML to process the data.

Snowflake has something called Snowflake Horizon, which has bundled various features of data security, data governance, and compliance together, and they have come up with the package. The tool has very good data security in terms of masking data. You can have different roles and assign policies in terms of who you want to be able to see data of a particular department, so you can assign based on department ID that only certain people can see the data. I found good features in my various other cloud databases, and compared to them, Snowflake data security and data governance are quite capable.

I don't think it is difficult to maintain. As the organization grows, maintaining policies, user roles, and data masking policies might become a little tricky in Snowflake. In AWS, we have a well-architectured framework where you have a defined framework or pattern, and you try to reuse it and modify it as needed. I don't see such kind of information or patterns largely available in Snowflake. I think as an architect, if we have a well-architectured framework for Snowflake, it will be useful. In terms of maintenance, I think the performance and all is okay in the tool. Data governance and policy management are a little bit tedious for the tool.

I recommend the tool to others. People should only be okay with the product's cost.

I rate the tool an eight out of ten.

I use the tool with visualization tools like Tableau and Power BI. We load the data into these tools and use them to build customer reports. We often need to write scripts to perform transformations before sending the data to the visualization tools.

The tool's performance is good. I think it's the best in the game right now. It usually charges per query. For example, if you run a SQL query on Snowflake with the same number of data records, it would take less than half the time compared to running it on Microsoft. It has good documentation. You can pick up Snowflake if you have previous knowledge of SQL.

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 from that, it's hard to point out any limitations in the tool.

I have been working with the product for four years. 

The tool is scalable. I've used it for datasets with more than ten million records.

I only put data in and modify data. Most of the time, I don't require technical support. We occasionally had downtimes, and the data engineer would escalate these issues to Snowflake to resolve them.

The solution's deployment is simple. You purchase the license on the Internet—I think there's only a free trial for thirty days—and set it up like a Gmail account. It takes less than a minute to set up. You can set up your Snowflake server or use an enterprise vendor like AWS or Azure. Recently, Snowflake has been moving away from third-party vendors. They want to set up their remote infrastructure.

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 you're running your queries frequently, your charges will be higher than running fewer queries.

I would give Snowflake a ten out of ten in terms of performance and a nine out of ten in terms of scalability. I rate the overall solution a ten out of ten. 

We use the solution extensively for reporting and analytics. We put data into it and publish reports. A report could be a dashboard. The data is used for data-driven insights and AI and MLOps. There are many use cases for the data that we procure on Snowflake.

The product has impacted collaboration across our teams. The correlation is quite easy. We use the solution because most of our life sciences and healthcare customers prefer it. Their preferences directly impact us as vendors and partners. We have to promote the same tools and technology they are familiar with.

The product is quite fast. There are several connectors in Snowflake that we could leverage for ingesting data. The data could be in zettabytes or petabytes. It is easily manageable.

The cost is a bit high. The storage cost and the extraction cost of data are high. The final invoicing cost will be higher if we do a rich data-oriented task on Snowflake.

I have been using the solution for close to three years.

The tool is stable and very powerful.

We have at least 1000 users in our organization. We will surely use the product in the future.

The solution is cloud-based. There is no on-premise solution. It has its own cloud. The installation is quite easy.

The solution is worth the money. It is good to use. It has a lot of features which are not available in other products. However, users must explore other products to control their costs.

Other products like Google Cloud, AWS, and Azure have competitive pricing. Snowflake costs 15 to 20% more than AWS and Microsoft Azure.

People who want to buy the product must initially use the free trial version. It can be installed on a desktop. The user can do a lot of R&D. We have a good playground. We can play with the components and learn them easily. We can learn how each component talks to each other, how the performance is, and how to create tables. There are a ton of tasks we can do.

After ingesting the data, we can perform advanced analytics and make models. The end users can do many things on the tool. It is quite an easy tool. I will advise any new user to install a free version. They will be able to learn about the product and get good insights when they work on their pilot project. Overall, I rate the tool a seven out of ten.

We use Snowflake as a database to store all the data we stream from the source system.

The best thing about Snowflake is its flexibility in changing warehouse sizes or computational power. If I want to change the computation with other tools like Netezza, I would have to add a hard disk to it. With Snowflake, being on the AWS side, changing warehouses provides me with faster execution of my queries.

The real-time streaming feature is limited with Snowflake and could be improved.

Currently, Snowflake doesn't support unstructured data. With Snowflake, you need to be very particular about the type of data in your source systems. It has to be in a proper structure. You cannot push data to Snowflake in any possible way.

I have been using Snowflake for a couple of years.

Snowflake is a stable solution.

Around 400 users are using the solution in our organization.

We previously used IBM Netezza. We switched to Snowflake in 2020 because it provided us control over its scalability and costing model.

The solution’s initial setup is comparatively easier.

Snowflake is a cloud-based, scalable solution that provides strong data security. Handling all the data is much easier in Snowflake, and it has a very nice interface to control user access. The administration of Snowflake is also comparatively easier.

Snowflake is a cost-effective solution.

Choosing Snowflake completely depends on the quantum of data your organization has and the requirements. Snowflake is suitable for someone looking for a scalable and cost-effective solution that provides quick analysis.

Overall, I rate Snowflake a nine out of ten.

Data warehousing is typically a rich guys' toy. Large enterprises are only able to leverage data warehouses for data analytics purposes. We wanted to change that and wanted to build a data warehouse template model for businesses across industries. 

If Snowflake was not around, we would have used Google's Big Query or Amazon's Redshift, or a MYSQL/Postgres database in a Windows VM (virtual machine). However, Snowflake made it a lot easier for us with loads of features such as encryption of data in motion and at rest, masking policies, time travel (to correct data load issues), controlled access based on roles, data sharing, third-party data from marketplaces, etc.

It helped us to build MVP (minimum viable product) for our idea of building a data warehouse model for small businesses. 

About ten years ago, force.com from salesforce.com offered a similar platform for us to build data warehouses. However, our staff with a data engineering background found it easier to build the data warehouse in Snowflake, with the easy-to-use SQL interface and RBAC models (role-based access control). The platform saved us money as it automatically shuts down the compute engines after about five minutes of idle time. Per second billing (above the first minute) is great. 

In my view, cost optimization for the computing power required by the ETL jobs, reports, and dashboards is the most valuable feature. Especially for startups, this helps us to keep cost spending within control without having to worry about manually shutting down the server when not used.  

As a Google partner, we like to leverage GCP (Google Cloud Platform). Snowflake supports GCP, AWS & Azure platforms. This works just fine for us. Encryption of data with multiple keys for both data in transit and data at rest gives us enough confidence to use snowflake for our customer 360 solutions.

Currently, we use Snowsight only to monitor the usage of the Snowflake environment by our users. However, if Snowsight can be improved, we can host our BI (business intelligence) environment also within Snowflake. In our case, to provide basic reports and dashboards, we started to use Tableau, Power BI, Looker, and Qliksense, depending on our customer preference.    

We are yet to figure out how to integrate tools, such as Liquibase, to release changes to our data warehouse model. If Snowflake could guide us with some easy-to-use integration (similar to DBT integration), that would be great.

I've used the solution since 2020.

Stable

Scalable

Support can be enabled in the Snowflake UI.

Neutral

In the past, we used Google Cloud SQL. However, Snowflake offered cost optimization among the many other useful features. They also introduced app building on top of the data hosted. 

The initial setup is not difficult. Google Search will lead us to articles that can guide us on the setup of users, roles, warehouses, and access controls.

We did the initial setup on our own, and it was not difficult.

We constantly monitor the usage with grafana dashboards to keep the ROI growing and to assist/ alert users about any wastage.

Many interesting features are available only in the enterprise edition. Check out the differences when you are evaluating the product: https://docs.snowflake.com/en/...

We considered MySQL and Google Big Query. We're also happy with Google Big Query. 

Snowflake is growing with newer features and capabilities. But not much success with Stream lit app. Big query + app sheet is an alternative that we're considering.

Our company uses the solution for building a data platform, data warehouse, and data transformation.

The product is somewhat used for data analytics, but it is mostly for data engineering.

The tool is good for handling large datasets, and since the tool is fully managed by Snowflake, you can scale up the compute part.

I don't think that the AI tools in Snowflake are good. AI tools in Snowflake can be improved. Even if the AI tools in Snowflake are good, I feel that it would be expensive. The cost of the AI part does not justify what you get from the product.

The price of the product can be lowered.

I think Snowflake should integrate with some tools like ChatGPT.

I have been using Snowflake for a year.

The product is scalable and can be considered a good fit for small and medium businesses.

I haven't directly contacted the technical support team of the product.

I have used Azure Databricks and Azure Data Factory. My company decided to use Snowflake since we wanted to be able to get up and running fast without much configuration-related mess. Snowflake doesn't give you the options with the configuration part since, by default, it is available out of the box. In terms of machine learning, Azure Databricks has the upper hand over other products.

The product's deployment phase was quite okay.

The solution can be deployed in a few days or up to a week.

The product's price range falls between average to a bit expensive range. I think the tool is worth the money if you use it properly. It is difficult for me to speak about the number of users who use the product. My company pays around a couple of thousand dollars a month to 10,000 dollars or more.

I think the main benefit is that with the tool, you can easily get things going without problems since you don't need to configure all the parameters manually. If you buy the tool for a bigger computing purpose, the engineer can pay more attention to the tool, and I guess after that, you can do more with the solution. I would ask others not to think about the data warehouses, as Snowflake takes care of such areas.

The benefits from the use of the product can be realized in around 40 minutes. It is a good technology for getting up and running quickly.

Snowflake is integrated with Azure Data Platform and other ETL tools in our company's ecosystem.

The integration capabilities of the product are good and you get what you pay for when it comes to Snowflake.

I rate the tool a seven to eight out of ten.

The solution is very good for building data warehouses. However, it has some limitations if we need it for more use cases.

All the features of the product that are needed for the data warehouse are good. The solution enables the ingestion of data and the usability of preferred languages while creating the data. The performance of the engine is good. The solution speeds up the process of onboarding. We can connect to different sources and get the data very fast. 

The tool does a very good job in reporting and data transformation. We can adapt it well to our needs. When we try to ingest data from many sources, it helps harmonize the data sources. It also helps with duplication and cleaning of the data. It is a pretty difficult and time-consuming task, and Snowflake helps us with it.

I do not like the proprietary format of the solution. Getting data out of the tool to third-party applications is difficult. The data science workloads must be improved. Snowflake has a lot to learn. There are better options in the market for data science.

I have been using the solution for almost three years.

The tool is stable. I rate the stability a nine or ten out of ten.

If we need to scale up, it will impact our costs. I work in a consulting company. We have a department dedicated to Snowflake. We have seven to eight people on our team. Our clients were medium-sized businesses with 1000 employees. They are focused on data analytics solutions. They also have departments for Azure and AWS. I rate the tool’s scalability a seven or eight out of ten.

I rate the ease of setup a seven or eight out of ten. The tool is deployed on the cloud. The time taken for deployment depends on the workload and how we build it.

The solution is expensive. I rate the pricing a nine out of ten.

We are partners. The impact of the solution’s automatic scaling feature on the workload depends on how we build our workload. The vendor must take a look at the market and how technologies evolve. The solution can do more in the area of distributed systems. If our use cases require data scientists, I rate the tool a three or four out of ten. I rate the tool a nine or ten out of ten for SQL data warehouse use cases. Overall, I rate the product a seven out of ten.

The solution is primarily used for data warehousing. 

It's a good tool. It is quite easy to manage. 

There are a lot of features. 

If you accidentally delete something, you can time travel and retrieve it. 

Within half an hour or even 15 minutes, you can set up a new data warehouse, and you can clone a table or whatever you like. 

It's easy to provide access to clients if they need to.

The solution is stable. 

It can scale well.

There is good online documentation via the community, and you can learn the solution on your own. 

These days, they are pushing users towards the GUI or graphical version. However, I am more familiar with the classic version. I'd like to continue to work with it using the older approach. That's just a personal choice. I prefer the database views like you would get on an SQL Server or other databases. 

I've been using the solution for two and a half years or so. I haven't used it for too long. 

The solution is stable and reliable. There are no bugs or glitches, and it doesn't crash or freeze. I've never had an issue when you connect it to your infrastructure. I'd rate the stability nine out of ten. 

We have 250 or more users on the solution currently. They are predominantly IT specialists, including engineers and developers. It's for those on the application side of development. The solution is scalable. I'd rate the scalability nine out of ten.

I've never directly dealt with technical support. We do have a direct contact. There are other people who might have. There might have been a version issue at some point. However, it wasn't something I dealt with. I've only interacted with the Snowflake community pages. 

We are currently moving everything from Oracle to Snowflake. 

We've used a combination of other tools in the past. We've used Microsoft's Stack, for example. We were using a SQL database in the past. 

We're migrating from Oracle right now. We have two people that handle the maintenance of the solution. A company may need two to four engineers to manage maintenance 24/7.

It's not difficult to deploy. It's pretty straightforward. It took us only a couple of minutes in order to get everything up and running. 

We pay a licensing fee to use the solution. It's paid monthly. My understanding is that it is not that expensive. We might have a specific extra cost surrounding running it on a private cloud. I'd rate the cost as six out of ten. It's moderately priced compared to others on the market. That said, I don't directly manage the account and don't directly deal with pricing. We have a contract of three to five years. 

I'm an end-user. 

Everything is on the cloud, and therefore I'm always using the latest version of the solution. It updates itself regularly. 

It fulfills our needs, and it's easy to pick up by looking at some reference guides. I'm still getting used to the GUI. I might find it even easier to use if I go through more formal training. Right now, I've simply learned it on my own. Overall, I'd rate the solution eight out of ten.