I would advise looking at your environment. Look at the workload and what you are trying to migrate. There is no one size fits all model. If you are a transaction system and you want to go with Snowflake, I would not advise this solution. If you are a reporting system and you want to migrate, Snowflake is the best choice. 

You also need to look at what kind of queries people are running. Don't assume that just because you are moving to Snowflake, you are going to cut down the cost by some factor. That is not going to happen. You need to really do a lot of homework and groundwork to know what kind of queries you're running and how can you avoid the compute costs. There is a lot of metadata available in Snowflake. You have to look at all that and then consciously try to improve the numbers. 

It is definitely a good tool and a good database without any adoption problems. Users who are SQL savvy can immediately adopt this solution. User onboarding is not really a huge exercise. It is a very simple exercise.

I would rate Snowflake an eight out of ten.

My past company was a Snowflake customer. This current company is not, however, it may be on the verge of it. 

I'm using the latest version of the solution. We switched clouds at some point. I was using it on AWS, and now it is on Azure. 

I'd recommend the solution to others. I would rate it nine out of ten. 

I think Snowflake is fantastic for both storing data and querying your data, but you should always maintain visibility into your costs. They can run up and get out of control if you're not aware of who's using Snowflake and why.

It's a great product. I think people don't need to stick to traditional Oracle systems and rather go for Snowflake. There you don't need to worry about any updates. It is a cloud product, so it automatically updates regularly. The advice is to get used to this way of working as it's new. You have to get familiar with the technology, and a little bit of the terminology. It's a very good product. I would rate it eight out of ten.

I rate this solution nine out of 10. 

It's good to use every day. It's the backbone of our entire reporting platform for both internal and external deployments of reports and visibility. We plan on continuing to grow our usage with it, as we put more and more people into our reporting platforms and bring our customers into more self-service that's going to increase the usage of the tool by the way that it actually serves up the information to the BI platform.

It's not at this time a transactional sort of database solution. It's truly only meant for data warehousing or data laking, and there's a lot of different ways to do role-level security. So you've got to have a good plan on that, but if you're looking for it to be the backbone of a transactional application, it's not the right tool for that.

I would rate this solution a ten out of ten.

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. 

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.

I would advise other people trying to use this solution to build a skill balance as it's quite difficult to work in Snowflake.

I would rate this solution as a whole a nine, on a scale from one to 10, with one being the worst and 10 being the best.

I rate the solution nine out of ten. 

Snowflake is ahead of the competitors because it's completely automatic and hands-off in terms of maintenance. Many of the competitor products have similar features to Snowflake, but what they call automatic still requires someone to understand it. If they give us 100 levers, somebody has to know what each of them does and when to pull them, whereas Snowflake is entirely hands-off.

My advice to potential customers is to have a team member who understands performance tuning and to figure out optimal credit usage ahead of time to avoid wasteful spending.

The implementation is essential because the solution provides a lot of power out of the box, and the initial configuration needs to be fit for purpose. If I have a relatively small use case where I don't need much power or don't have much data, the product needs to be configured for that. As opposed to an external case where I might need high power for a government job, for example, then the configuration needs to be scaled up.

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.

Snowflake is growing with newer features and capabilities. We're glad that we chose it. 

I'm a consultant and end-user.

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

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

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

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

I'd rate the solution eight out of ten. 

I would advise others to check costs when implementing any changes, such as new BI tools or a new data source. Set up different warehouses for your different tools so that you can track cost.

I would rate this solution a nine out of ten.

I would advise ensuring that you have the expertise with domain knowledge in Snowflake. The time from initial concept to deployment could be expedited extremely fast. Just from our internal learnings, we see that our time to production has increased month over month.

I would rate it a six out of ten just because we're unaware or naive to the full capabilities of the product. However, I would highly recommend it in terms of setting up data warehousing internally over an Azure solution, such as Synapse, or something else.

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

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

I would rate this solution a seven, on a scale from one to 10, with one being the worst and 10 being the best.

Snowflake is very useful as a data lake and as a data warehouse. Also, it has a lot of features with respect to data science. We are not there yet, but if there are any specific use cases around compute, data distribution, and data sharing, then Snowflake is a tool to be considered.

I'd rate Snowflake a seven out of ten.

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

I would rate Snowflake a nine out of ten.

I 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.

I rate Snowflake an eight out of ten.

I would rate Snowflake a nine out of ten.

We are working on two solutions for Snowflake, one for the cloud and one for on-premises. It has good documentation. If someone goes through it, they will quickly understand how it works. However, Firebolt's documentation is more comprehensive. If I need faster results, I'll prefer the Firebolt; if I need performance, I'll use Snowflake.

Overall, I rate it a nine out of ten.

The solution is more straightforward to use than the other IDBMS tools. It has a simple query process. Its computing time is less as well. One can easily have access to it. I rate it as a nine.

The key part is skill set because Snowflake is all SQL-driven data warehousing. Internally, we have some SAP BW development resources, and they need to learn and move on to understanding SQL-based coding and custom data warehousing concepts.

I would rate Snowflake a nine out of ten.

My advice for anybody who is considering Snowflake is that it is a really good product, especially if you are having issues with Big Data. It is not good for a typical OLTP environment, such as a small table.

I would rate this solution an eight out of ten.

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.

I give the solution an eight out of ten.

Deciding between Azure Synapse and Snowflake can be difficult, as the best choice depends on one's own use case. Ultimately, it comes down to the available connectors; the product with more connectors is likely the better option. When making a decision, one should consider which other sources they would want to get data from and where they want to send data to. This can help inform their product selection.

I would recommend this solution to others.

I rate Snowflake a nine out of ten.

I would rate this solution 8 out of 10.

I rate Snowflake a nine out of ten.

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.

You must try it out. It is a wonderful product. I would also recommend trying out other products, such as Yellowbrick, and doing a comparison. Redshift has also come up with some serverless options. BigQuery is also there. BigQuery is as easy as Snowflake. So, my recommendation or advice is to try out these things and then pick the one that suits you. I don't have any bias towards any of the products. I have an impartial opinion about all the cloud data warehousing products.

I would rate it a nine out of 10.

I would rate it an eight out of 10.

Overall, this is a helpful tool with a friendly interface. 

I would rate this solution an eight out of ten.

I would recommend the SaaS version for their organization. It is not complicated to use. Establishing a private link with current cloud services has been challenging so I would recommend having some kind of a block.

I would rate this solution a nine out of ten. 

I rate Snowflake eight out of 10. 

I would give Snowflake a seven out of ten.

I would rate the solution a nine out of ten. Snowflake is the market leader in data warehousing and cloud database. I don’t think that it has a direct competitor. I would suggest you give Snowflake a try if it fits your use case. You can open up a trial version for 45 days and convert it to a regular account. There are different tiers in the solution like business critical, standard, etc. The tool gets updates every week.

The biggest conversion problem we've seen so far is when someone had a large number of stored procedures that were SQL-based, as opposed to external stored procedures written in C or whatever the DBMS would support. Converting those stored procedures either to a SQL script or to a stored procedure or function that's based on JavaScript is the biggest challenge that most people we've dealt with are having. That's because they have to relearn the language they're writing their logic in.

I would easily rate it an eight out of 10.

In terms of performance the solution is good when compared to the analytical workloads and good in comparison to Redshift or BigQuery. The performance is on a slightly higher level, but when it comes to real-time performance, NoSQL is better than Snowflake, but that's in rare cases and depends on the particular requirement. Overall, for the analytical use case, Snowflake is a good solution and in terms of availability, it's a cloud data warehouse, so  they do replication and the like. 

It's important to understand your business needs, because these tools need to be properly modeled and they have their own advantages. If you're new to Snowflake, it's worth starting slowly for one month and move gradually, because if it's a complex system and you move everything to Snowflake without good architecture, then you can get stuck with the original problem. It's worth taking the time to make it efficient and then design modeling; there are SnowPro certifications as well. 

I rate this solution an eight out of 10. 

My advice to someone who is looking at Snowflake is that if they are looking at analytics tools in addition to warehousing and certain advantages of cloud computing, then I would suggest Snowflake. But if they are just looking for the warehousing part where you will later just use another solution on top of it, then I would not suggest Snowflake.

On a scale from one to ten where one is the worst and ten is the best, I would rate Snowflake as an eight or nine. Let's say 8.5.

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

I rate Snowflake an eight out of ten.

On a scale from one to ten, I would give Snowflake an eight.

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

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

I give the solution an eight out of ten.

For organizations that do not wish to be confined to one type of hyperscalar, such as VM Azure, I recommend Snowflake as it provides greater flexibility.

I give the solution an eight out of ten.

I advise people to do as much research as they can before utilizing the Snowflake.

I would recommend this solution to others.

I rate Snowflake an eight out of ten.

We're customers and end-users.

We're using the latest version of the solution. I can't speak to the exact version number.

I'd rate the solution at a nine out of ten. We've been mostly very happy with its capabilities.

I'd recommend the solution to other users and companies.

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.

Snowflake is easy for business users to implement, allowing them to start small and grow big.

I think people are still debating on whether they should still continue with S3 and add Snowflake or, whether they should take away S3 and completely rely on Snowflake.

I would rate this solution an eight out of ten.

Snowflake has a lot of capabilities and performance. However, the tool is not a silver bullet and can do everything. If you designed what you need according to the tool, then everything is going to be okay.

This is true for any tool. Many people start the projects without validating what they are going to expect to have at the end, they receive a big surprise. They were thinking that the tool has this capability and it doesn't have it or perhaps it has the capability but the design you have does not work correctly.

If you see the percentage of projects in the different customers in many places, such as in Mexico, Florida, and Miami. Snowflake is a tool that is currently being used but has not been in the past. There is not a lot of history.

I rate Snowflake a six out of ten.

We have not used Snowflake long enough to better rate it. If we had a lot more formal education or had more information or reference manuals our experience would be better.

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.

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

I would rate this solution an eight out of ten.

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.

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

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

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

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.

We're partners with Snowflake. We've been partners for just under a year at this point.

I'd definitely recommend the product. It's worked quite well for us. 

A new customer needs to understand, however, that they need a roadmap of at least five years when they are deciding on their data warehouse. They should compare costs and sizing to make sure they are getting the solution that makes sense for their current and future needs. 

The solution integrates well with other applications, and if you need it to integrate with existing applications, you still should check to make sure it's possible.

I wouldn't necessarily recommend Azure over Snowflake, as they aren't really a good comparison. Snowflake is more focused on data repositories and data warehouses. AWS does give you many options, however.

I would definitely recommend this solution. 

I would rate this solution a nine out of 10. 

My advice to those wanting to implement Snowflake is it is easy. However, the way to choose to implement your data in the warehouse matters. When we started to implement our data with Snowflake, we also switched to a metadata-driven approach, but the method depends on the people involved in the implementation. Overall, the implementation of Snowflake follows similar principles as any other data-warehouse implementation except many aspects are a lot easier and helpful. 

I rate Snowflake an eight out of ten.

The solution is very easy and flexible to integrate with any type of API.

I rate Snowflake a nine out of ten.

We're a customer. We don't have a business relationship with the solution.

Users considering adding the solution should understand that Snowflake can be used only for transactional processing, not for analytical processing. If they want to go for transaction processing, they can go for Snowflake and if they want to go for analytical processing, they should look at or go for an Oracle database.

I'd rate the solution seven out of ten.

I rate this solution eight out of 10 and recommend it to other users. 

My advice for anybody who is considering implementing Snowflake is that from a user's standpoint, it is a good product. Having a database in a cloud setup means that you don't have to scale and it has got many features already included.

For our use case, we found this Snowflake was good enough and did not need any enhancements. I recommend using it.

I would rate this solution a ten out of ten.

I recommend the solution to others and rate it as a nine. It efficiently processes the data and gets reports as well.

One of the concerns related to Snowflake is about longevity in terms of how long can we use Snowflake. It is a big question in the market. It is a new baby in the market, and we don't know for how long will it trend. It has some big competitors. Firebolt claims to be the number one in this area. They have much better features than Snowflake. I would not say that Snowflake is the best and in the right position at this point in time. Snowflake is good for the next year, but Firebolt is going to bring it down.

I would rate Snowflake an eight out of 10.

It is a good solution. At the moment, I can't find another product that is better than Snowflake, but it needs better ETL functionality, easier configuration, and cheaper support. All products have got some limitation.

I would rate Snowflake an eight out of ten.

I would recommend this solution to others. We plan to keep using it. 

I would rate Snowflake a nine out of ten.

I give Snowflake a nine out of ten.

Snowflake is being used at the enterprise level.

If an organization is interested in embarking on its cloud journey and Snowflake fulfills its requirements, I would recommend it as a viable solution.

I would recommend this solution. I would rate Snowflake an eight out of ten.

My advice for anybody who is implementing Snowflake is to start small, then prove out the value and you can grow.

I would rate this solution an eight out of ten.

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

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

I would recommend this solution to others and we are going to keep using the solution in the future.

I rate Snowflake an eight out of ten.

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.

I would rate Snowflake an eight out of ten. 

I think the solution is suited to big companies because they tend to have lots of data. The more data you have, the more you need power and scalability to process it. I would recommend finding a good partner already familiar with the solution for implementation. It's good to have someone familiar with the architecture.

I rate this solution a 10 out of 10. 

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.

I would rate it a seven out of 10.

Personally, if I have the choice, I would rather recommend Snowflake to my clients over a product from Microsoft, for example. They have some overlapping functionality, but they also have some separate stuff. Snowflake does not have the size to develop at that pace but personally, I find them a more sympathetic company than Microsoft.

I would rate this solution an eight out of ten.

We're partners with Snowflake.

The difference between Snowflake, and, for example, Azure, is that there is real separation between the computer and storage. Snowflake is the only one that's really separate and it's much simpler to scale or shift data. It makes everything much easier.

One of the best options on the market right now is to have a cloud-only setup. Not everyone is using the cloud, but everyone will catch up.

I'd rate the solution nine out of ten. If the user interface was better and they had a few more features and did some useability tweaks it would be perfect. Also, it's hard to get the data out of Snowflake, and that's a real issue design-wise.

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

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

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

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

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

We're partners.

While I can't speak to the version number we are using, we're always on the latest version of the solution.

Snowflake is a good product. It is quite robust and scalable. However, a few of the functions are a little complex in Snowflake. 

I would rate the solution at a nine out of ten.

The best advice I would give is to push for a POC. Pick a couple of use cases where you think you could quickly get value and just see how quickly you can get it implemented. One of the key features of Snowflake is that you can get it up and running straight away. 

I would rate it a 10 out of 10.

I would rate Snowflake an eight out of ten.

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

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

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

We don't recommend a cloud typically. We leave it to the customer. If the customer has AWS, and then we sell Snowflake on AWS. If the customer has Google, we sell Snowflake on Google or Azure, or if they have Azure, we sell Azure. They may even have a private cloud. We don't force the customer to buy a particular cloud. We go with the customer's preference from their cloud services because Snowflake works on all three clouds.

In general, I would rate the solution eight out of ten. It does what it says it will, and I have yet to hear of customers complaining about its capabilities.

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

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

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

I would rate this solution an eight out of ten.