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.
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?
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.
Buyer's Guide
Snowflake
June 2025

Learn what your peers think about Snowflake. Get advice and tips from experienced pros sharing their opinions. Updated: June 2025.
861,490 professionals have used our research since 2012.
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

Sr. Solution Architect at a insurance company with 1,001-5,000 employees
Great features with excellent virtual warehousing and good architecture
Pros and Cons
- "For us, the virtual warehousing is likely the most valuable aspect."
- "I would like to see a client version of the GUI."
What is our primary use case?
We're running a POC to test scalability, performance, on-demand resource management, workload management, et cetera. The security aspect will also be important for us.
What is most valuable?
The product offers a lot of great features.
Architectural-wise, it's got great architecture. That's what we are looking for. It's kind of decoupled from storage and has virtual warehouses. We like that we can travel and keep things virtual. For us, the virtual warehousing is likely the most valuable aspect. You can spin up as many virtual warehouses that you want. That's quite useful as a feature.
What needs improvement?
I haven't found that the solution is lacking any features. It's quite complete.
I would like to see a client version of the GUI. Right now, it is a web GUI, which has stored the SQL, the worksheets. We are asking for that from Snowflake. We'd like to understand how can we save these worksheets on our local desktop. That is not there at this point.
For how long have I used the solution?
I've been using the solution for about the past year as part of a POC.
Which solution did I use previously and why did I switch?
In the past, we've used an SQL server. On the cloud side of it, we do have some experience. Snowflake, however, is the new data warehouse solution that we are looking into it.
Which other solutions did I evaluate?
If necessary, we may have to get into Synapse, and do a kind of a pilot project with that as well. We may evaluate them both to see which is better. We are not there yet. We are just working on Snowflake.
What other advice do I have?
We are a direct customer and end-user.
We've been using the solution during a POC for the last year or so. It's a pilot project to test its feasibility for our company. We're just starting to get performance stats and stuff like that.
I'm not sure which version of the solution we are currently using. I don't recall the exact version number. Usually, people are running the latest version. Whatever the latest available option is is likely the number we are on.
I'd rate the solution at an eight out of ten. We're still in the POC phase, however, based on what we have seen, we are quite satisfied.
Which deployment model are you using for this solution?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsoft Azure
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Buyer's Guide
Snowflake
June 2025

Learn what your peers think about Snowflake. Get advice and tips from experienced pros sharing their opinions. Updated: June 2025.
861,490 professionals have used our research since 2012.
BI & BIG DATA Director at Malam-Team
A good platform that can handle structured and semi-structured data and is very fast to implement and integrate
Pros and Cons
- "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."
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
In future releases, it can also support full unstructured data.
For how long have I used the solution?
We have been using this solution for a year.
What do I think about the stability of the solution?
It is stable.
What do I think about the scalability of the solution?
It has very good scalability. Your data can grow in the platform. We have at least 50 users of this solution in an organization.
How are customer service and technical support?
Their vendor is wonderful. I only have good words for them.
How was the initial setup?
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.
What's my experience with pricing, setup cost, and licensing?
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.
What other advice do I have?
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.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer. Partner
Founder & CIO at a computer software company with 11-50 employees
Reasonable pricing with a straightforward setup and a good user experience
Pros and Cons
- "The technical support on offer is excellent."
- "There are always a few operation updates here and there that can be made."
What is our primary use case?
We primarily use the solution to build some cost-effective solutions for a data warehouse, mostly for all non-transactional data.
What is most valuable?
The solution is very fast. It's not clunky or slow.
The product, overall, is quite inexpensive. It's very cheap to use.
The solution is extremely user-friendly and easy to navigate. The user experience is very good.
The initial setup is pretty straightforward. It's simple.
We found that the initial setup was pretty easy.
The solution has been stable and has provided good overall performance.
A company can easily scale the solution. It's not too difficult to pull off.
The technical support on offer is excellent. They're helpful for the most part.
What needs improvement?
There are always a few operation updates here and there that can be made. However, overall, there aren't any features or glaring shortcomings. It's pretty good. We can't complain.
While the solution is quite inexpensive, there is always a push from clients that want it to be cheaper in the future.
For how long have I used the solution?
I have about six years' worth of experience with the product. I've been using it for a while. I'm comfortable with its aspects. I've used it over the last 12 months as well.
What do I think about the stability of the solution?
The stability is very good. There are no bugs or glitches. It doesn't crash or freeze. It's reliable. The performance is good.
What do I think about the scalability of the solution?
The product scales quite well. If a company needs to expand it, it can do so without any problem.
We deal mostly with clients that have medium to large-scale organizations. It works well for both.
How are customer service and technical support?
Technical support has been excellent. I'd rate them nine out of ten. They are knowledgeable and responsive. We are quite happy with the level of assistance we receive if we need help.
Which solution did I use previously and why did I switch?
We've used a few other solutions including MySQL and a few other notable databases.
Right now, we are looking for some other options as well.
How was the initial setup?
The initial setup is quite simple. It's a straightforward process. It's not overly complex. A company shouldn't have any issues with the implementation process.
What about the implementation team?
We are implementors. We can implement the solution for clients if they need us to.
What's my experience with pricing, setup cost, and licensing?
The product is very reasonably priced. It's quite cheap to use. It's less expensive than, for example, Oracle.
What other advice do I have?
We are implementors of the solution.
We are using previous versions of the solution. It may not necessarily be the latest version all the time.
I'd advise other organizations to try it out and play with it a bit to see if it would fit their needs.
Overall, I would rate the solution at a nine out of ten. We've been mostly very happy with it.
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?
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Senior Information Management Architect at Raken
I like how quickly the solution can be implemented
Pros and Cons
- "The features that I have found most valuable are the ease of use, the rapidness, how quickly the solution can be implemented, and of course that it's been very easy to move from the on-premise world to the Cloud world because Snowflake is based on SQL also."
- "It would benefit from an administration that allows you to be aware of your credit consumption once you have the service so that you may be sure how many credits you are consuming when you use the platform and to make sure that you are making the most efficient use of these resources. In other words, to improve their interface so that you may monitor the consumption of your credits on Cloud."
What is our primary use case?
We are a consulting company so our primary use depends on the niche that we are providing the services to and on which of the different versions they have. I think we are mainly using Snowflake Enterprise.
In general, it is being used for integrating information. Snowflake is a database platform, it gives information to support analytic needs, such as advanced data analytics like machine learning. In some of those cases it is also used for descriptive analytics, for instance BI.
How has it helped my organization?
One of example of how Snowflake has improved a client's organization is the democratization, it makes information available to more of the users.
What is most valuable?
The features that I have found most valuable are the ease of use, the rapidness, how quickly the solution can be implemented, and of course that it's been very easy to move from the on-premise world to the Cloud world because Snowflake is based on SQL also.
What needs improvement?
I think that the area of improvement with Snowflake is to improve the administration. It would benefit from an administration that allows you to be aware of your credit consumption once you have the service so that you may be sure how many credits you are consuming when you use the platform and to make sure that you are making the most efficient use of these resources. In other words, to improve their interface so that you may monitor the consumption of your credits on Cloud.
I also heard from a company we work for that it could be more user-friendly because it provides some tools but they are not user-friendly.
Additionally, it would be very helpful if Snowflake integrated machine learning and some other advanced analytics features within their language or product capabilities. Right now, they do it through some other company where you have to buy these capabilities from other vendors. There are some customers that don't have complex needs for machine learning or advanced analytics so they don't have to buy it from another vendor but can use it from the product itself if they have it.
For how long have I used the solution?
The whole company has been using Snowflake for about three years.
What do I think about the stability of the solution?
In terms of stability, so far it is very stable.
What do I think about the scalability of the solution?
Snowflake is very scalable. Our client companies where we implement Snowflake are medium to large sized. These companies have offices in different parts of the world, not just some regions, but companies with office users in different parts of the world. We are dealing with international companies. Their tendency is to increase the use of the Snowflake platform. It would serve all the analytical needs in these companies.
How are customer service and technical support?
I have not directly experienced the technical support. It's not part of my job to be involved on those kind of issues, but we constantly receive information as a partner from them and we are very in good touch with them and with the people we are working with, meaning the representatives that are within the Latin American market, which is where I work. They are very open and very fast with communication.
How was the initial setup?
The initial setup is easy. Full deployment takes a few weeks. The initial deployment for the first initiatives might take weeks. It's not complex, really. You may have it loaded after a full day and already providing results or interacting, but there are some other companies that have to be implemented to extract and consume the information from the database. But it's very easy.
Which other solutions did I evaluate?
There have been a couple of other solutions that we've been participating in the evaluation process of and some others that have been included in the decision process, including Redshift from AWS and also Azure Synapse from Microsoft.
For instance, AWS Redshift looked like it was easier to implement and to be adopted by the technical users, the programmers and database programmers. So far it has been far easier to adapt this technology. I'm not saying that AWS is a better technology. It's very complex, but at least what I've seen is that for them, it looks like it's been easier to use the first time.
We liked that Snowflake is able to be used as a multi-Cloud service - it can be used in AWS Cloud, Azure Cloud, or Google Cloud. Whereas AWS, or even Synapse, can only be used in their corresponding networks.
What other advice do I have?
I would definitely recommend Snowflake.
On a scale of one to ten, I would give Snowflake an eight.
I give it an eight out of 10 due to its room for improvement in the user interface for the monitoring of the credit consumption and that the user experience is not friendly. And also because the machine learning is lacking some advanced analytic features.
Which deployment model are you using for this solution?
Private Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer. partner
Associate Manager at a consultancy with 501-1,000 employees
A secure and fast solution with inbound and outbound share features and good integrations
Pros and Cons
- "Its performance is a big advantage. When you run a query, its performance is very good. The inbound and outbound share features are also very useful for sharing a particular database. By using these features, you can allow others to access the Snowflake database and query it, which is another advantage of this solution. It has good security, and we can easily integrate it. We can connect it with multiple source systems."
- "I am still in the learning stage. It has good security, but it can always be more secure."
What is our primary use case?
We are using it for our security products. We have a trial account, and we are using the trial database and practicing on top of it. We have the latest version of this solution.
What is most valuable?
Its performance is a big advantage. When you run a query, its performance is very good.
The inbound and outbound share features are also very useful for sharing a particular database. By using these features, you can allow others to access the Snowflake database and query it, which is another advantage of this solution.
It has good security, and we can easily integrate it. We can connect it with multiple source systems.
What needs improvement?
I am still in the learning stage. It has good security, but it can always be more secure.
For how long have I used the solution?
I have been using this solution for a few months. I am in the learning stage.
What do I think about the stability of the solution?
It is stable. Its performance is very good.
What do I think about the scalability of the solution?
It is scalable. We have four users who are using Snowflake.
How are customer service and technical support?
We are going through the online version, and we don't find any difficulty with this.
Which solution did I use previously and why did I switch?
I also use Azure. Snowflake has more advantages than Azure.
How was the initial setup?
There is no installation as such. After you register with Snowflake, you get a demo database, which you can configure and use. It only takes around 30 minutes.
What about the implementation team?
I did it myself.
What's my experience with pricing, setup cost, and licensing?
Currently, we have a trial account, so we don't need a license. After our project starts, we would need a permanent license.
What other advice do I have?
I would recommend this solution to others. We plan to keep using it.
I would rate Snowflake a nine out of 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?
Other
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Lead Data Analyst at a wholesaler/distributor with 1,001-5,000 employees
Feature-wise complete, good speed and performance, and easy to configure
Pros and Cons
- "Its speed and performance were the most valuable. Easy configuration of Snowflake in any cloud was also a benefit."
- "Its pricing or affordability is one of the big challenges. Pricing was the only thing that we didn't like about Snowflake. In terms of technical features, it is a complete solution."
What is our primary use case?
It was only a workshop with training to know the tool. We were just testing the technology, and it was just a demo of the tool. We wanted is to connect switches with IoT and use Snowflake as an engine to process all the big data. It was on top of AWS, but our infrastructure is on top of the Google Cloud Platform.
The intention was to see if we can process on the front-end that we have. We have a console that processes a big amount of data. Instead of using BigQuery, we used Snowflake to see if it is cheaper than using BigQuery, but Snowflake wasn't cost-effective. In the end, we didn't go for this solution. We just saw how it can be implemented, but we never bought anything.
How has it helped my organization?
We don't have a metric, but I would say that the processing time was a key benefit and value-add. It provided on-time processing.
What is most valuable?
Its speed and performance were the most valuable. Easy configuration of Snowflake in any cloud was also a benefit.
What needs improvement?
Its pricing or affordability is one of the big challenges. Pricing was the only thing that we didn't like about Snowflake. In terms of technical features, it is a complete solution.
What do I think about the scalability of the solution?
Its scalability is great. We have data processing of one terabyte per month.
How was the initial setup?
It was not complex. Our implementation strategy was to put Snowflake on top of Google Cloud solutions instead of BigQuery, but BigQuery was better in price. So, BigQuery won in this case instead of Snowflake.
What about the implementation team?
We got the guidance directly from Snowflake. They have a technical expert for Latin America.
What's my experience with pricing, setup cost, and licensing?
We used Snowflake to see if it is cheaper than using BigQuery. It was just to maintain the cost or the KPI regarding the cost of connectivity by users. Snowflake wasn't cheaper than BigQuery, and its affordability was the main issue.
What other advice do I have?
My advice is to consider Snowflake when you have more customers. I wouldn't consider Snowflake until I have sufficient customers.
Whether we will consider Snowflake in the future depends on how BigQuery behaves. If the cost of BigQuery starts increasing and becomes similar to Snowflake, we're going to switch. If not, we're going to remain with BigQuery.
We might also consider other similar solutions, such as Yellowbrick, or switch to another cloud solution, such as Azure or AWS, depending on the price. Right now, we are paying about $2,000 per month. Our goal is to have the total cost of everything to be around $3,000 per month. It is more or less our goal for KPI kind of thing.
I would rate Snowflake an eight out of 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: My company does not have a business relationship with this vendor other than being a customer.
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: My company does not have a business relationship with this vendor other than being a customer.

Buyer's Guide
Download our free Snowflake Report and get advice and tips from experienced pros
sharing their opinions.
Updated: June 2025
Popular Comparisons
Azure Data Factory
Teradata
Oracle Exadata
OpenText Analytics Database (Vertica)
Microsoft Azure Synapse Analytics
Dremio
VMware Tanzu Data Solutions
Amazon Redshift
BigQuery
Oracle Autonomous Data Warehouse
SAP BW4HANA
Amazon EMR
Apache Hadoop
AWS Lake Formation
IBM Netezza Performance Server
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?