I mostly build or design data warehouse analytics solutions using Snowflake.
IT Consultant at Independent Consultant
Straightforward deployment, stable, and scalable
Pros and Cons
- "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."
What is our primary use case?
How has it helped my organization?
The productivity across the teams that use Snowflake I believe is higher than it would be without the solution.
What is most valuable?
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.
What needs improvement?
Snowflake needs transparency over costs and pricing.
Buyer's Guide
Snowflake
March 2025

Learn what your peers think about Snowflake. Get advice and tips from experienced pros sharing their opinions. Updated: March 2025.
844,944 professionals have used our research since 2012.
For how long have I used the solution?
I have been using the solution for three years.
What do I think about the stability of the solution?
I give the stability an eight out of ten. We rarely have issues.
What do I think about the scalability of the solution?
I give the scalability an eight out of ten.
Which solution did I use previously and why did I switch?
I have used many on-premise solutions in the past and also Azure Synapse Analytics.
How was the initial setup?
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.
What about the implementation team?
Depending on the complexity of the implementation, we may need to use a third party or help from the vendor.
What's my experience with pricing, setup cost, and licensing?
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.
What other advice do I have?
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.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsoft Azure
Disclosure: I am a real user, and this review is based on my own experience and opinions.

Technical Lead at Wipro Limited
Allows us to connect to the database and import required tables into our system
Pros and Cons
- "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."
- "These aren't as crucial, but there are common errors sometimes where the database is down, or a table is nullified and a new table is added and you are not given access to that. With those errors, you don't have permissions."
What is our primary use case?
We're using Snowflake for Power BI Cloud. We had a cloud version of Snowflake, so we were connecting to the Snowflake database and importing required tables into our system, Power BI Desktop. From there, we linked those tables and created a semantic layer, an internal layer between the frontend and backend, and then we tuned the data. Then we used both the tables to tie into the dashboards that we developed. The dashboards show the sales information or marketing information.
It's a cloud solution.
What is most valuable?
I like the entire database. 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.
What needs improvement?
Sometimes when I'm trying to refresh the data, my different application or tool has to connect to its backend database through the connection I create. Sometimes, I face some issues like not having permissions. These aren't as crucial, but there are common errors sometimes where the database is down, or a table is nullified and a new table is added and you are not given access to that. With those errors, you don't have permissions.
For how long have I used the solution?
I have been using Snowflake for a year.
What do I think about the stability of the solution?
It's stable.
What do I think about the scalability of the solution?
The scalability is good. It handles a lot of data, and the processing speed is very high.
How was the initial setup?
It's straightforward. You have to have a rule, database names, and a schema name.
When somebody deploys it and gives me the URL and the required tables to use, I use the URL and configure it from the frontend side, reporting side that could be more like Power BI or Tableau, and I start using it.
What other advice do I have?
I would rate this solution 8 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.
Buyer's Guide
Snowflake
March 2025

Learn what your peers think about Snowflake. Get advice and tips from experienced pros sharing their opinions. Updated: March 2025.
844,944 professionals have used our research since 2012.
Senior Snowflake Data Architect @ COOP Financials NC at a tech services company with 1,001-5,000 employees
High performance, useful features, and scales well
Pros and Cons
- "The most valuable features are sharing data, Time Travel, Zero Copy Cloning, performance, and speed."
- "The UI could improve because sometimes in the security query the UI freezes. We then have to close the window and restart."
What is our primary use case?
We use the solution for a data warehouse and we generating reports and dashboards.
How has it helped my organization?
Snowflake has improved my organization because of its high performance compared to the old way we used to operate with Microsoft SQL Server. We are migrating everything from SQL Server to Snowflake. It used to take a lot of time to query the database but now it is done a lot faster, we receive millions and billions of reports. This is a major benefit because it is our major use case.
What is most valuable?
The most valuable features are sharing data, Time Travel, Zero Copy Cloning, performance, and speed.
The solution is very easy to run the queries. We have a built-in query optimizer in Snowflake that works very well.
What needs improvement?
The UI could improve because sometimes in the security query the UI freezes. We then have to close the window and restart.
There should be an IDE concept similar to the Java IDE or Eclipse feature. I should be able to see all of the functions available on a particular object. Every time we need to go to the Snowflake documentation and look if there are any methods we need. It is hard to remember everything, go and search, and use that that eventually found method. If it was possible to list out all the methods and functions available in an object that would help the developer's a lot.
In an upcoming release, we should be able to send or receive data from external systems but this is not able to be done. There should be built-in logging and monitoring features, we should not need to be dependant on third-party solutions, such as Splunk. There should be more DevOps features to reduce the usage of third-party tools. If these features were part of Snowflake it would be a fully functional complete solution.
For how long have I used the solution?
I have been using Snowflake for approximately two and a half years.
What do I think about the stability of the solution?
They claim zero maintenance support and from my experience, I would agree with that statement. When I was on a previous project we had a lot of support for the Netezza platform we were using. We had approximately twelve people, three onsite and seven offshore. When we migrated from Netezza to Snowflake we reduced the number of people required and kept only some of the team as developers. There is very little support required for this solution. Stability is very good in SnowFlake.
What do I think about the scalability of the solution?
The scalability is built into this solution as being on the cloud. It is able to scale in all directions. Additionally, they have a multi-cluster warehouse, and based on the business use case it is very good.
There are approximately 4,000 portals. However, we do not know how many users our clients have that are using their portals.
We are building new data warehouses and we are migrating from SQL Server to Snowflake.
How are customer service and technical support?
The support is very good. We create tickets and they respond with a solution.
Which solution did I use previously and why did I switch?
We were using SQL Server previously and we switched because of the increased performance, multi-clustered shared environment, scalability, and we wanted to use a cloud-based solution.
How was the initial setup?
Everything with the installation went smoothly. I believe when I joined the company Snowflake was already here. They bought the Business Edition that is encrypted everywhere because they are a financial insurance company and most of them choose the Business Edition because of the security.
What about the implementation team?
The company I work for used SnowFlake integrators for implementation assistance.
Which other solutions did I evaluate?
I have evaluated Eclipse and IBM Netezza.
What other advice do I have?
The solution is very easy and flexible to integrate with any type of API.
I rate Snowflake a nine out of ten.
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.
Practice Head, Data & Analytics at a tech vendor with 10,001+ employees
Exceptionally good technology that addresses data warehousing challenges and is built and designed in a good way
Pros and Cons
- "The way it is built and designed is valuable. The way the shared model is built and the way it exploits the power of the cloud is very good. Certain features related to administration and management, akin to Oracle Flashback and all that, are very important for modern-day administration and management. It is also good in terms of managing and improving performance, indexing, and partitioning. It is sort of completely automated. Everything is essentially under the hood, and the engine takes care of it all. As a data warehouse on the cloud, Snowflake stands strong on its ground even though each of the cloud providers has its own data warehouse, such as Redshift for AWS or Synapse for Azure."
- "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."
What is our primary use case?
It is used in my company as well as in my client's company. We are a system integrator, so naturally, we need to have the centers of excellence and competencies in Snowflake.
What is most valuable?
The way it is built and designed is valuable. The way the shared model is built and the way it exploits the power of the cloud is very good. Certain features related to administration and management, akin to Oracle Flashback and all that, are very important for modern-day administration and management.
It is also good in terms of managing and improving performance, indexing, and partitioning. It is sort of completely automated. Everything is essentially under the hood, and the engine takes care of it all. As a data warehouse on the cloud, Snowflake stands strong on its ground even though each of the cloud providers has its own data warehouse, such as Redshift for AWS or Synapse for Azure.
What needs improvement?
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.
For how long have I used the solution?
I have been using this solution for close to three years. I kept a tab on Snowflake and its progress since it came into the market.
Which solution did I use previously and why did I switch?
Personally, I have worked extensively with Oracle, SQL Server, and Teradata. SQL Server has the Fast Track Data Warehouse (FTDW) appliance. Oracle has both the database and the appliance. I haven't worked on Parallel Data Warehouse, which is a big one offered by Oracle. Teradata is an appliance in itself. There is also Metadata. I haven't worked on DB2.
All of these had their own lacunae. Data warehouses had their own problems. There were failures, challenges, and difficulties in adoption, and all of these have been addressed by Snowflake a big way. It has tried to marry the best of both worlds in terms of turnaround time, scalability, adoption, and seamlessness.
I hail from a classical data warehouse background. Snowflake has been kind of a silver bullet. It is trying to meet the best of both worlds. I wish I could do much more on Snowflake, but I'm tied up with many other things, which is why I'm not able to concentrate that much, but it is an exceptionally good technology.
How was the initial setup?
Its initial setup is very simple, which is its plus point. It is not at all a problem. You only need to understand a bit of the cloud ecosystem. When Snowflake is on Azure or AWS, you need to understand
- What exactly is happening?
- How these two are handshaking with each other?
- What part Snowflake is playing?
- How Azure or AWS is complementing it?
If these things are clear, the rest shouldn't be a problem.
What other advice do I have?
This could be something that might be debated upon, but Snowflake has two parts to it. One is the data warehouse itself, and the other one is the cloud. It is important to know about the cloud in terms of:
- How a cloud functions?
- How a cloud orchestrates through its services, domains, invocation of services, and other things?
- How a cloud is laid out?
For example, let's take AWS. If AWS is invoking Lambda or something else, how will S3 come into the picture? Is there a role of DynamoDB? If you're using DynamoDB, how would you use it in the Snowflake landscape? So, cloud nuances are involved when we speak of Snowflake, and there is no doubt about that, but a more important area on which Snowflake consultants need to focus on is the core data warehousing and BI principles. This is where I feel the genesis of Snowflake has happened. It is the data warehouse on the cloud, and it addresses the challenges that on-prem databases had in the past, such as scalability, turnaround times, reusability, adoption, and cost, but the genesis, principles, and tenets of data warehousing are still sacrosanct and hold good. Therefore, you need the knowledge or background of what a data warehouse is expected to be, be it any school of thought such as Inmon school, a Kimball school, or a mix. You should know:
- Data warehouse as a discipline.
- The reason why it was born.
- The expectations out of it in the past.
- The current expectations.
- What being on the cloud would solve?
These things on the data warehouse side need to be crystal clear. The cloud part is important, but it is of lesser essence than the data warehouse part. That's what I see, personally, and I guess that's the way the Snowflake founders have built the product.
As a data warehouse, I would rate Snowflake an eight out of ten.
Disclosure: My company has a business relationship with this vendor other than being a customer: reseller
AVP Enterprise Architecture at a financial services firm with 501-1,000 employees
A perfect solution that delivers as promised and makes it easy to manage the overall ecosystem
Pros and Cons
- "The overall ecosystem was easy to manage. Given that we weren't a very highly technical group, it was preferable to other things we looked at because it could do all of the cloud tunings. It can tune your data warehouse to an appropriate size for controlled billing, resume and sleep functions, and all such things. It was much more simple than doing native Azure or AWS development. It was stable, and their support was also perfect. It was also very easy to deploy. It was one of those rare times where they did exactly what they said they could do."
- "Their strategy is just to leverage what you've got and put Snowflake in the middle. It does work well with other tools. You have to buy a separate reporting tool and a separate data loading tool, whereas, in some platforms, these tools are baked in. In the long-term, they'll need to add more direct partnerships to the ecosystem so that it's not like adding on tools around Snowflake to make it work. They can also consider including Snowflake native reporting tools versus partnering with other reporting tools. It would kind of change where they sit in the market."
What is our primary use case?
I have used it in my previous company. It was just a SQL server data warehouse using reporting tools on top of it. It was an on-premise SQL server environment, and it was a typical data warehouse use case, but we wanted to do things faster and more cost-effectively.
We used it to modernize our data warehouse. We didn't want to invest more in on-premise servers, and we were looking for a way to quickly get more data joined together.
How has it helped my organization?
It had definitely improved the way our organization functioned at the time.
What is most valuable?
The overall ecosystem was easy to manage. Given that we weren't a very highly technical group, it was preferable to other things we looked at because it could do all of the cloud tunings. It can tune your data warehouse to an appropriate size for controlled billing, resume and sleep functions, and all such things. It was much more simple than doing native Azure or AWS development.
It was stable, and their support was also perfect. It was also very easy to deploy. It was one of those rare times where they did exactly what they said they could do.
What needs improvement?
Their strategy is just to leverage what you've got and put Snowflake in the middle. It does work well with other tools. You have to buy a separate reporting tool and a separate data loading tool, whereas, in some platforms, these tools are baked in. In the long-term, they'll need to add more direct partnerships to the ecosystem so that it's not like adding on tools around Snowflake to make it work. They can also consider including Snowflake native reporting tools versus partnering with other reporting tools. It would kind of change where they sit in the market.
For how long have I used the solution?
I have been using this solution for about three years.
What do I think about the stability of the solution?
We didn't run into anything. We had outages for a couple of seconds, but they were related to Amazon or AWS. They weren't related to Snowflake.
What do I think about the scalability of the solution?
We scaled it a little bit. We didn't have a lot of data to scale, as a lot of companies do. We only had a couple of terabytes of data, which is insignificant for a cloud platform.
The development team had three or four people getting data in. Then report people were also using the platform, but they didn't really have to know that it was Snowflake because they were going at it through a reporting tool. There were probably 30 or 40 people writing queries against our reporting tools, which were, in turn, using Snowflake.
How are customer service and technical support?
They were really good. They were very responsive. There were never any issues with them. I would give them a ten out of ten.
Which solution did I use previously and why did I switch?
I've used a lot of different data warehousing solutions at different companies.
How was the initial setup?
It was easy as pie. In a couple of hours, it was up and running, and we were loading the data in. We had a fairly senior developer for that. He knew SQL server and queries very well. If you're used to developing in any type of SQL environment, you can jump in and use Snowflake really quickly.
What's my experience with pricing, setup cost, and licensing?
It is per credit. It has a use-it-as-you-go model. We bought a chunk of 20,000 credits, and they were lasting us for at least a year. We didn't have the scale of data like a much larger company to consume more credits. For us, it was very inexpensive.
Their strategy is just to leverage what you've got and put Snowflake in the middle. It doesn't make it expensive because most of the organizations already have reporting tools. Now, if you were starting from scratch, it might be cheaper to go a different way.
What other advice do I have?
If time to value is your primary goal, then I would recommend going for Snowflake over one of the other cloud providers.
I would rate Snowflake a ten out of ten. It is one of the few products in which everything demos well. It actually did everything they showed in the demos. We really couldn't find any gotchas in it. It kind of delivered as promised.
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.
Vice President of Business Intelligence and Data Engineering at a comms service provider with 201-500 employees
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.
Senior Software Engineer at a consultancy with 10,001+ employees
Reasonably priced solution but credit performance could be improved
Pros and Cons
- "The features I found most valuable with this solution are sharing options and built-in time zone conversion."
- "I see room for improvement when it comes to credit performance. The other thing I'd like to be improved is the warehouse facility."
What is our primary use case?
Our current plan and use case for this solution is to migrate the data from on-premises to the cloud. We are currently using on-prem monitor data and providing it on the cloud. We are using Snowflake so that once the data is in there, we are trying to create shares over it so that external systems can't consume it.
What is most valuable?
The features I found most valuable with this solution are sharing options and built-in time zone conversion.
What needs improvement?
I see room for improvement when it comes to credit performance. The other thing I'd like to be improved is the warehouse facility.
In the next release, I'd like to see easier connectivity to the on-premises tools.
For how long have I used the solution?
I have been using this solution for about three years.
What do I think about the stability of the solution?
My impression from using this product for the last three years is that it is quite stable.
What do I think about the scalability of the solution?
My impression is that this is a scalable solution. There are around 200 users of this solution at our company, including three administrators.
How was the initial setup?
The initial setup process was not that complex and it took around six months.
What about the implementation team?
The implementation was done by an in-house team.
What's my experience with pricing, setup cost, and licensing?
My impression is that the pricing of this solution is reasonable.
What other advice do I have?
I would rate this solution a seven, on a scale from one to 10, with one being the worst and 10 being the best.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Manager at SSM VIT Global Solutions
It can exchange data with downstream systems and other vendor partners as well
Pros and Cons
- "I like Snowflake's data exchange capabilities. It can exchange data with downstream systems and other vendor partners as well."
- "There are some challenges with loading unstructured data and integrating some message queues or brokers. In one project, we had a problem connecting to one of the message queues and we had to take a different route altogether on Microsoft Azure."
What is our primary use case?
My current client is migrating from an on-premise data warehouse to the cloud, and they need to consolidate the data lake. I'm using Snowflake to develop the data lake and build data bots for certain functionalities. I've also used Snowflake to aggregate and clean data for my client's analytics.
What is most valuable?
I like Snowflake's data exchange capabilities. It can exchange data with downstream systems and other vendor partners as well.
What needs improvement?
There are some challenges with loading unstructured data and integrating some message queues or brokers. In one project, we had a problem connecting to one of the message queues and we had to take a different route altogether on Microsoft Azure.
For how long have I used the solution?
I started using this product about two years ago at my last company. Now, I'm a registered Snowflake partner, so working with Snowflake for one of my clients.
What do I think about the stability of the solution?
My clients haven't faced many stability challenges. It is a relatively new product that's still evolving. They're using it mainly for POCs, so they haven't faced any problems.
What do I think about the scalability of the solution?
The most valuable aspect of Snowflake is its scalability. The volume of data, which I have seen across almost in terms of five terabytes and other terabytes of data, I didn't see issues.
How are customer service and support?
Snowflake technical support is good. At my previous company, they had a customer success officer for critical accounts, and they were accessible. When I registered as a partner, I also got a quick response from support. I would rate their support eight out of 10.
How would you rate customer service and support?
Positive
How was the initial setup?
Setting up Snowflake isn't complex. I've not seen any challenges.
What's my experience with pricing, setup cost, and licensing?
They have different pricing structures based on data usage. I think they have three or four tiers you can scale through. Most of the clients see an advantage from this type of licensing. That's the reason they go for it. It's priced competitively with other solutions.
What other advice do I have?
I rate Snowflake eight out of 10.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsoft Azure
Disclosure: I am a real user, and this review is based on my own experience and opinions.

Buyer's Guide
Download our free Snowflake Report and get advice and tips from experienced pros
sharing their opinions.
Updated: March 2025
Popular Comparisons
Azure Data Factory
Teradata
Microsoft Azure Synapse Analytics
Vertica
Amazon Redshift
Dremio
BigQuery
Amazon EMR
Oracle Autonomous Data Warehouse
AWS Lake Formation
SAP Business Warehouse
IBM Db2 Warehouse on Cloud
Firebolt
Buyer's Guide
Download our free Snowflake Report and get advice and tips from experienced pros
sharing their opinions.
Quick Links
Learn More: Questions:
- What are the key reasons for choosing Snowflake as a data lake over other data lake solutions?
- What is the major difference between AWS Redshift and Snowflake?
- What is the biggest difference between Apache Hadoop and Snowflake?
- Which solution do you prefer: Oracle Exadata or Snowflake?
- Which is better - Azure Synapse Analytics or Snowflake?
- How to achieve sub-second query performance with JSON data (~1B rows) in Snowflake?
- Which is better for Snowflake integration, Matillion ETL or Azure Data Factory (ADF) when hosted on Azure?
- Which ETL or Data Integration tool goes the best with Amazon Redshift?
- What are the main differences between Data Lake and Data Warehouse?
- What are the benefits of having separate layers or a dedicated schema for each layer in ETL?