Snowflake Analytics Reviews

I mainly use Snowflake Analytics for creating the data lake in Snowflake, specifically the medallion architecture, where we have our data lake with different layers including staging, raw, and then the final layer where our data model sits, enabling us to do reporting on the top of this data model, and we also maintain sandboxes for AI/ML use cases.

Majorly, we have an entire data lake in Snowflake Analytics with a huge volume of data and perform data analysis and prepare reports for the same.

Regarding data model transformations, I have used features such as functions with tasks and user-defined functions, which help in transformation. Snowflake Analytics notebooks and Snowpark allow writing procedures in JavaScript, Python, or Java, providing strong support for transformations.

I am using Snowflake Analytics on the cloud.

There are many capabilities which Snowflake Analytics offers that I find valuable, such as the storage and compute engine that allows working with any cloud system such as AWS or Azure, alongside its efficiencies in storage computation and cost-effectiveness, which saves money compared to on-premise systems.

We also have features such as pre-cached results, Time Travel, and fail-safe, which are very useful for restoring data if deleted accidentally, and the streams and data pipes that facilitate real-time ingestion are great features as well.

Snowflake Analytics offers multiple new connectors, allowing me to connect it with Kafka, and with Snowpark, I can work with any programming language such as Python, Java, or Scala for data processing and analysis.

The data sharing feature offered by Snowflake Analytics is good because it allows sharing specific sets of data to end customers or users from different Snowflake Analytics accounts without exposing the entire dataset for data security reasons.

Snowflake Analytics' support for machine learning models and real-time insights has enhanced significantly. Originally, it wasn't strong in AI/ML, but now it has multiple models and forecasting capabilities, providing good competition to tools such as Databricks and Spark.

In BI, I have worked majorly with Microsoft Power BI, and the integration with Snowflake Analytics is very easy. The way we integrate Snowflake Analytics with other on-premise systems just requires the warehouse details, username, passwords, and the account name, along with multiple options such as client ID and credentials for logging in and creating a session.

The end-to-end encryption provided by Snowflake Analytics is very important because, in my previous firm, working in finance and investment management, data encryption is necessary due to the sensitive nature of customer data and the involvement of people's money. It's crucial to have encryption in transit and at rest, along with data masking features which Snowflake Analytics offers.

There are some minor issues encountered with Snowflake Analytics, such as problems when working with identity or row number generating different results or issues with referential integrity, which are being reported on the Snowflake Analytics website, indicating they are looking into these problems for future updates.

I would prefer Snowflake Analytics to improve their support response times, as sometimes the responses we receive are not very prompt and ticket assignments may not be timely.

I have been working with Snowflake Analytics for four years now.

Snowflake Analytics has been stable and reliable in my experience. In our production environment, it has been running for about four to five years without issues.

Maintaining security and data governance becomes easier with an entire data lake in place, and the scalability improves performance. We can scale the warehouses as needed based on query performance, and the overall cost-effectiveness enhances resource utilization while ensuring secure access to data sets and business use cases.

I often communicate with the technical support of Snowflake Analytics. Initially, for developers, we had a team from Snowflake Analytics that facilitated multiple sessions, and recently we had a two-day session where the Snowflake Analytics team provided a demo on Cortex AI and its features.

I would rate the technical support from Snowflake Analytics an eight based on professionalism and how helpful they are.

Positive

Earlier, we were predominantly working on an on-premise system. Besides Snowflake Analytics, we explored other options such as Databricks for creating a data lake, but Snowflake Analytics looked more promising.

I have used Snowflake Analytics functionalities extensively, working with semi-structured, unstructured, and structured data with all offerings such as stream, Snowflake Analytics pipelines, Snowflake Analytics Snowpipe, Snowflake Analytics notebooks, and Snowflake Analytics integration with Microsoft Power BI. Recently, I have started exploring the AI models and functions which Snowflake Analytics is offering, such as document extraction or image analysis using AI Cortex.

Snowflake Analytics has positively impacted my company by making data sharing easier among multiple applications and teams.

Snowflake Analytics is definitely affordable, which is why our organization decided to adopt it.

We save money transitioning from on-premise systems to Snowflake Analytics, benefiting from its cloud infrastructure, which offers scale-up and scale-down computing capabilities and enables having a data lake in one place.

Apart from pricing, factors such as performance, easy integration with the cloud, scalability, and cost-effectiveness influenced our decision to choose Snowflake Analytics.

I rate Snowflake Analytics a nine out of ten.

Once we receive all the data throughout the day from all the restaurants in one country for a restaurant client, we organize the data, remove duplicate entries, and remove any inconsistencies, then process the data into our data warehouse by using Snowflake. From there, by using Snowflake Analytics, we extract the data and build BI dashboards. Sometimes we also use machine learning algorithms to learn from that data and build a model that we can share with the business users so they can make good business decisions that can help them gain profits.

We use Snowflake, and before we used Power BI and Looker, but now after integrating Snowflake with Snowflake Analytics, we are mostly using Snowflake Analytics, although we are using Power BI and Looker for other tasks. Our main use case is building dashboards.

The other aspect is how the query performance is high due to its columnar storage and also automatic optimization, allowing for scaling down during weekdays when there is less data and scaling up during weekends or festivals when the data can be huge. Because of this automatic scaling, if there is less data, we are using only 5 GB instead of 10 GB, which reduces the storage level, and consequently, the cost can be reduced. This automatic scaling and optimization saves us a huge amount of money for our project.

Snowflake Analytics has impacted our organization positively by providing faster query performance and better scalability. Previously, we faced issues with slow queries due to traditional systems, but within Snowflake, we can assign separate virtual warehouses for reporting as well as data processing, ensuring that it does not impact tool performance and does not delay reporting to business users. Analysts can run complex queries without affecting ETL workloads due to this separation, which has improved our speed of reporting, and our business users have expressed happiness due to how fast we are generating reports during peak hours.

The accuracy of Snowflake Analytics is good, but sometimes the SQL query recommendations are not optimized. However, since the AI is newly integrated into Snowflake, I believe it will optimize queries within one to two months based on our project, making the accuracy acceptable but with the need for improvement in optimization.

I advise others looking into using Snowflake Analytics to have prior knowledge in SQL and usage of BI tools, and to go through the documentation and YouTube tutorials before using the tool. Snowflake Analytics is very user-friendly, enabling anyone with prior knowledge in data engineering and analytics to use it easily. My overall rating for this product is 8 out of 10.

Snowflake Analytics' data sharing feature has been instrumental for us because we were working with huge data sizes. Our workflow involved dumping data initially into an AWS S3 bucket, then sharing it with Snowflake Analytics, and then exporting it back into S3. The setup is very quick and easy with Snowflake Analytics.

For machine learning models, we require a lot of initial analytics on data, and Snowflake Analytics has had a significant impact in this area. When we preprocess data for machine learning models by splitting data into multiple parts, we were dealing with data in the billions. Snowflake Analytics helped us filter that data and check all aspects of it, such as data purity and identifying where we were missing values. In these scenarios, Snowflake Analytics has helped us gain insights about our data and prepare it for machine learning models.

My company is a partner of Snowflake Analytics through a tie-up that provides us with credits. There is a credit system in Snowflake Analytics that we use for our work.

End-to-end encryption provided by Snowflake Analytics is very important. The feature encrypts data in SSH format, and you can also decrypt that data if you have the key, which provides a very high amount of encryption security.

Snowflake Analytics has played a major role in improving our data model transformations. As I mentioned, we had very large data volumes, and it increased our productivity by allowing us to do things very quickly and receive results rapidly. Earlier, we used to do a lot of preprocessing using traditional methods and Python, but with Snowflake Analytics, we reduced the time and effort required for coding.

In my opinion, Snowflake Analytics can be improved by introducing more features, such as additional integration options. I remember using Snowflake Pro, which allows exporting direct data into the S3 bucket, but there were a couple of things that were lacking at that time, particularly data transformation during exports, and I would suggest adding some minor features.

I would like to see more integration features, specifically with Amazon Web Services, in the next release of Snowflake Analytics. Most companies are using these cloud technologies, so additional features and some transformation capabilities while exporting to different data buckets would be very helpful.

I have five years of total IT experience, and in that time, I have used Snowflake Analytics for more than one year for data processing, data manipulation, and data exporting with AWS.

The initial setup for Snowflake Analytics is very easy, but there are some difficulties concerning security permissions that you need to go through, since privacy is a concern. Apart from that, I don't see any hurdles with the initial setup.

I have not practically used Snowflake Analytics' integration with BI tools, but I know about it and understand that we can integrate Snowflake Analytics with BI tools. My review rating for this product is 8.

In our organization, regarding Snowflake Analytics, we have a data engineering team who manages all the work on the back-end side, starting from the data load and managing all those pipelines. The only thing where we utilize Snowflake Analytics is running queries and performing UAT to ensure they are performing well.

Apart from that, we also created views and stored procedures in Snowflake Analytics.

In our company, we use Snowflake Analytics as a cloud data warehouse. Most of the projects are migration projects where clients migrate from a particular data warehouse or database to Snowflake Analytics. Our data engineering team acquires all the client requirements information, performs all the data engineering work, and puts that data in Snowflake Analytics. After that, they inform the analytics team that the data is pushed to Snowflake Analytics. We can then connect with any BI tool the client wants and start our development.

I heard about the Cortex functionality, which Snowflake Analytics has recently introduced, where you can use LLM models to do analytics, but those things are still yet to be explored by us. Our data engineering team is exploring all those capabilities.

The latest interface of Snowsight UI has added good capabilities and the interface is excellent. I use both the classic UI and the newer Snowsight, and it is good to work with Snowflake Analytics.

As we are a Snowflake Analytics partner company, most of our projects use Snowflake Analytics as a backend. While doing migrations, we connect Snowflake Analytics with multiple BI tools such as Tableau, Power BI, and Sigma Computing. There is also analytics engineering work where people migrate flows from other platforms. When connecting with Snowflake Analytics, we easily understand the process of fetching database schemas and other elements.

I do not see any areas that could be improved with Snowflake Analytics.

In the analytics domain, we are at a beginner to intermediate level, not at the SME level.

We were experiencing errors while running reports and making connections. The Power BI team raised tickets for both Power BI and Snowflake Analytics, and their responses were very good. They connected with us to resolve the issue. The issue occurred due to the ODBC driver installed in our systems.

What I have seen during my time working on these projects is that the Snowflake Analytics documentation is excellent. They provided everything thoroughly and concisely with screenshots, making it very clear to understand.

Positive

It is important that Snowflake Analytics provides end-to-end encryption for us. The keys are encrypted using RSA keys in Snowflake Analytics, though I am not entirely sure about the details. The data governance team manages all security, compliance, and related aspects. The data engineering team handles data cleansing and loading/unloading of data, after which the analytics team begins their work.

The data engineering team would provide better insights on Snowflake Analytics support for machine learning models in real-time insights. We previously connected with our Snowflake Analytics team for a project migrating from SSIS, SSRS reports to Power BI. In the Power BI report builder, where we created paginated reports, we experienced connection errors. Both the Power BI and Snowflake Analytics teams provided good responses and helped resolve the issues.

I rate Snowflake Analytics 9 out of 10.

Our primary use case involves building a cloud data warehouse to support business analytics. The business requires analytics, and we are building this ecosystem to help senior management with data-driven decision-making.

The internal design engine and the columnar database are particularly valuable. These features reduce input and output memory, which is crucial in handling large data sets. The solution fulfills the business requirement for scaling and analytics. Snowflake Analytics supports data security with a single sign-on feature and complies with framework regulations, which is highly beneficial.

The advantages of Snowflake Analytics outweigh the disadvantages. However, if it offered flexibility similar to Oracle and supported more heterogeneous data sources and database connectivity, it would be even better. PySpark is emerging as a competitor, so Snowflake Analytics needs to bridge any gaps between them.

I have been using Snowflake Analytics for almost one year.

Based on my experience over the past year, Snowflake Analytics is stable, scoring around eight point five to nine out of ten.

Snowflake Analytics is very scalable, rating nine to nine point five out of ten. It supports both horizontal and vertical scaling effectively.

The technical support for Snowflake Analytics is excellent based on what I have heard from others. It is responsive, and people find it very good.

Positive

I have supported Redshift, AWS, and Azure in the past, but my clients have migrated to Snowflake Analytics due to their business requirements where Snowflake is more popular and better suited.

During the initial setup, a feasibility study and impact analysis were required. We reviewed the existing schema and business objects, developed a strategy, gathered a team, executed the plan, and conducted post-migration checks.

Snowflake Analytics has impacted our operational costs positively, making it economical in handling large data volumes.

Snowflake Analytics is quite economical. It does not appear to incur significant extra expenses beyond the solution's initial cost. However, a complete pricing analysis is still in progress.

Snowflake Analytics has a bright future and is capturing the market across various domains such as life sciences, BFSI, and supply chain. It is recommended for others due to its robust features and capabilities. I rate the overall solution around 8 to 8.5.

I have to get the data, load it into the warehouse, and analyze it to gain insights from the data.

It is a data offering where I can see data lineage, data governance, and data security. Snowflake has a streaming capability to work with real-time streaming data and delta tables. 

Additionally, task management, job scheduling, and connecting multiple data sources unify my data across internal and external sources. The system ecosystem for analytics is enhanced, and AI capabilities are incorporated.

Most features are already available. Perhaps AIML integration might be further needed, or Snowflake is already implementing it. AIML-based SQL prompt and query generation could be an area for enhancement.

For the last year, I have been exploring Snowflake.

I don't see any problem as of now.

Storage is unlimited because they use S3 if it is AWS, so storage has no limit. Compute capability depends on the machine, load, and cluster being used. It all depends on the load and the computing resources being utilized. They provide up to 64 CPUs, as I remember.

Mostly, the problems are in-house or internal, so we solve them internally. As of now, I haven't had a chance to work with support.

Positive

The cost savings will be realized.

Snowflake is better and cheaper than Redshift and other cloud warehousing systems. It's economical.

I cannot make a direct comparison these days between Redshift and Snowflake, however, Snowflake is definitely better than Redshift.

I rate the overall solution nine out of ten.

I mainly do data analytics on Snowflake databases, which might be structured, unstructured, or semi-structured.

It's basically for relational data, majorly. In some cases, it's for real-time data processing.

In most cases, Snowflake improves our operational efficiency if we optimize the warehouse. If not, it may hit you hard. Some customers don't analyze the workload but update the compute. If you don't utilize it properly, it may affect costs because monthly costs depend on the virtual warehousing. Credits can go up significantly, so you need to be very careful. Otherwise, it's about 90% to 95% efficient.

We've also got customers getting into AI optimization. Snowflake Analytics' predictive analytics elements, which incorporate AI, are good and easy to integrate.

It supports structured, semi-structured, and unstructured data. Plus, it can be optimized for various use cases because it has separate compute and storage power. This sometimes creates good data processing and sharing capabilities.

So, for processing data, it can be easily optimized and supports structured and unstructured data.

In terms of cost. Many customers face issues with the expenses on Snowflake. The pricing visibility is complex. If you understand pricing, you can estimate costs, but if not, it can be challenging. They need to provide better cost visibility upfront. 

For example, credits are not always utilized properly, which isn't easy for new users. A more user-friendly cost calculator would help, as the current one requires expertise to use effectively. These things are not easy for someone who is new to Snowflake, unlike Azure's calculators, which give good visibility into the cost. 

It does have a calculator, but you need to be skilled in using it. Otherwise, it's hard to estimate the total cost for future loads.

For additional features, there could be its own AI model like Google has Gemini. Snowflake can come up with those kinds of features for Analytics. If you can just type in your prompt and get answers, especially for Analytics people on the client side, they will love that.

Like, in Google's Gemini, you type the prompt and get the answers based on the data available. If they come up with that kind of AI and UI, it will be easier for clients to analyze their data. They can just type a query like, "What is my highest selling product?" They don't have to write a complex query.

I have been using it for three years. 

There is no issue. I would rate it an eight out of ten for stability. 

Scalability is good with Snowflake because it's a SaaS product. It can be deployed onto any of the IPaaS platforms.

It is good. Whenever we require optimum performance or if there is any performance issue, we can easily scale up and scale down Snowflake, depending on the load. It's very good for that. We mainly use Snowflake on AWS and Azure, and it has been pretty good with no issues.

I would rate the scalability a nine out of ten. We normally have enterprise businesses as our client. Smaller ones don't normally go for Snowflake or a database solution like this.

I had connections mostly through my onshore counterpart, who is an ex-Snowflake employee, so we never faced challenges.

Deployment doesn't take much time. Configuration of the warehouse might take time, but otherwise, it shouldn't take long.

Normally, it takes an hour, but due to validations and approvals, it can take a couple of days.

Deployment model:

Our customers are mostly on public cloud. Hybrid is mainly when they need to bring data from on-premises to the cloud. The data movement is there, but it's mostly on the public cloud. There are some on the private cloud, but not much. I haven't come across many.

It's not costly if you configure it properly to ensure optimal performance. People don't configure it properly, which is why costs go up. So it depends on the knowledge of the customer.

I would recommend you don't go for Snowflake every time. It depends on your use case. Analyze the use case and then decide whether to go with Snowflake or another database. For structured and semi-structured data, Snowflake is a good choice.

Overall, I would rate it an eight out of ten. 

I use Snowflake primarily for writing SQL queries, which includes tasks like creating common table expressions (CTEs) and stored procedures, as well as database optimization. In data processing, I organize data into logical structures and manage large datasets. I have about four to five years of experience using Snowflake Analytics for these tasks.

In terms of improvements to my organization, Snowflake Analytics allows for a quick and efficient run of large queries. This has been crucial, as it's important that the database can handle queries from very large tables.

One of the distinctive features of Snowflake is its ability to handle large datasets efficiently. For instance, running a considerable query on Microsoft SQL Server may take up to thirty minutes or an hour, while Snowflake executes the same query in less than three minutes. 

Snowflake Analytics can also embed Python code seamlessly, allowing for diverse tasks within the database. There are features such as filtering and sorting, which make it easier to use than other databases. The fact that Snowflake charges per query, which incurs only a minimal cost, is favorable compared to other databases.

There are areas for improvement in Snowflake. Navigating the user console can be challenging, particularly when looking for details like the account ID. Additionally, having an on-premises application for querying the Snowflake database directly from a computer would be a great enhancement.

I would say four to five years.

The stability of Snowflake is good. I have never found it necessary to contact technical support.

I have not reached out to customer service, so I have no experience with them.

Positive

We previously used Microsoft SQL Server. We switched to Snowflake since it significantly improved the speed of query execution.

The initial setup was straightforward and easy to manage due to Snowflake's new web services.

Snowflake charges per query, which amounts to a very minor cost, such as $0.015 per query. This is different from Microsoft or other databases that base charges on the infrastructure.

I would not say there is additional advice. 

I rate Snowflake Analytics around a nine out of ten.

In the cloud, we have various databases like Cosmos DB, customer databases, blob storage, and so on. We don't want to handle everything as JSON files. If data needs to be in a structured format, Snowflake is a good option because it's easy to deploy. 

Additionally, Snowflake takes care of the underlying storage layer, offers good performance, and has a very good distributed architecture through virtual warehouses. 

Plus, there's the option for security, handling data duplicates, and data governance – it's all in one package. And it can seamlessly integrate with streaming data, which is awesome.

And it also integrates with Python and machine learning, similar to Databricks now. So, it's a good competitor for Databricks.

Snowflake has enhanced our data warehousing capabilities. Mainly, it's the infrastructure. We can distribute data and create a multi-warehouse architecture for performance optimization. 

We don't need to worry about memory or storage, and Snowflake Cloud handles licensing and storage. The integration with Azure lets us deploy data seamlessly from our data lake to Snowflake storage using copy scripts with transformations.

Moreover, we primarily use the data sharing feature to store our logs, especially for machine learning use cases where structured data is essential. 

Previously, we used Hive with MongoDB integration and a Hadoop layer. Now, we use Informatica to load unstructured data into Snowflake as a target. Then, we convert it into a structured format, making it usable for machine learning.

Snowflake's integrated features actually made the most significant impact on our analytics efficiency. Security, dynamic data masking, data cloning, data sharing, data sampling, ETL processes, and streaming processes – it's all in one product. 

It's also a good product for batch processing. While Databricks may be superior for machine learning, Snowflake is still maturing in that area.

Moreover, Snowflake's performance speed was crucial to our project success when it comes to reporting capabilities. We use MicroStrategy as our centralized reporting front-end, which relies on Snowflake. 

Also, when migrating data to a data warehouse, we can directly load it into Snowflake using Snowflake's integration with Azure Blob or AWS S3, enabling the infrastructure through Informatica or Azure Data Factory (ADF). This allows for a simple architecture with Snowflake functioning as a data lake, an intermediate transform version, or a source for sector data. And there's no complexity in handling JSON data.

Handling JSON files can be very complex, especially for hierarchical data, which needs to be split. Snowflake makes this very easy to handle.

Scaling is very high – there's no problem for scaling purposes. The learning curve is very small. And there are a lot of advanced features like handling duplicates, security, data governance, data sharing, and data cloning.

Data sharing and data sampling are very easy – data can be shared with a third party with just a simple command. We also have stored procedures which can be deployed in the cloud, eliminating the need for relational databases. Snowflake acts like a relational database, but without the old-fashioned complexities.

It can be a leader in the industry. If you compare Snowflake to something like Databricks, you'll need to know cloud infrastructure access, Python coding, and more – the learning curve is much steeper with Databricks.

With Snowflake, those core, familiar SQL skills allow you to handle data seamlessly. You don't need to worry about the infrastructure, security complexities, or the typical cloud-based architecture. This software can truly act as a data lake. 

Instead of going for Blob storage, Azure SQL Database, or Databricks – especially compared to Databricks – Snowflake is very easy to learn and implement for all your analytics needs.

There are a few areass of improvement. 

• Databricks may be superior for machine learning, Snowflake is still maturing in that area.

Also, machine learning in Snowflake isn't as advanced as in other products. I haven't heard of any successful industry-wide use cases of machine learning implemented in Snowflake. It might take a couple of years to reach the same level as Databricks.

• Python integration is still an upcoming capability within Snowflake.  

• Additionally, loading data from the cloud to Snowflake is straightforward, but we still lack the capability to do the reverse – from Snowflake to the cloud.

I have been using it for two years. 

I would rate the stability an eight out of ten. 

I would rate the scalability a nine out of ten. We can instantly scale up. It is the main thing in Snowflake. 

There are around 28 end users using it. Most of the job roles include developers and data engineers. 

The customer service and support are actually good. 

Positive

Since Snowflake is a newer tool, there's a vast amount to learn, and not as many study materials or videos are publicly available. We had to do a lot of self-exploration. 

Additionally, being a vendor-based product, there can be challenges integrating Snowflake with third-party tools outside of the seamless Azure and AWS integrations. For example, integrating with SAP ERP or SAP HANA might not be feasible at this time.

Deploying Snowflake within the cloud is very simple. There's no infrastructure to manage, just security, access, and pricing provisions. However, third-party integrations might be a different story.

It's very easy, taking just a couple of hours – definitely easier than deploying something like an Oracle server.

User accounts are separate from compute and storage – there's a decoupling in Snowflake. This means separate handling of storage and compute.

Overall, the pricing model is very competitive compared to products like Databricks, especially for streaming and business analytics use cases.

It is not overly expensive. I would rate the pricing a six out of ten, with ten being expensive. 

I would definitely recommend using it but with a caveat: it's an excellent tool if your organization is fully in the cloud. 

For hybrid cloud environments, it's not as feasible.

Overall, I would rate the solution an eight out of ten. It lacks built-in front-end reporting capabilities. You'll need to integrate with a third-party tool like Power BI.

Also, Snowflake's graphical features are limited since it's primarily a database. However, if it offered built-in features for front-end reporting dashboards that support enterprise needs, it could compete with Power BI.

We use Snowflake as a database or data warehouse. We rely on AWS S3 services for computing and storage. It provides security, including role-based access and data encryption, and is handled at the database level in Snowflake. We use DBT for the data loading process, applying business logic to create the final tables in DBT, which then load the data.

Some features include the ability to handle semi-structured data, such as JSON. It supports various database sizes. Also, storage and compute resources are independent.

I have been using Snowflake Analytics for seven to eight months.

It's all hosted on AWS because Snowflake doesn't have its storage. Both computing, such as clustering and storage, are managed through AWS services like S3. Since S3 already provides scalability, Snowflake leverages those built-in properties.

When we started configuring Snowflake for our project development, we contacted support. They provided guidance on implementing security measures, including multi-factor authentication. The vendor required us to use MFA because it adds an extra layer of security, ensuring the protection of both development and production environments.

To enable multi-factor authentication, we were asked to download and use a separate application to receive notifications and approvals. This added security measure was mandatory to enhance the system's overall protection.

Positive

I worked with Redshift, and it's introduced many new features since then. Most recent projects have used Snowflake or other databases like SQL Server. While Redshift is still an option, Snowflake has gained more popularity.

Both Redshift and Snowflake are columnar databases, and they share similar features, such as the ability to handle different database sizes. Redshift has incorporated these features in its newer versions. If a project is fully integrated with AWS, clients might prefer Redshift as their data warehouse instead of Snowflake. It depends on their specific needs and infrastructure.

The initial setup wasn't too difficult or straightforward. Some configurations, like setting up files, followed a typical procedure. Certain steps, such as enabling multi-factor authentication, are essential nowadays for adding an extra layer of security. This has become common in most software services to enhance security.

The configuration process wasn’t overly challenging. It took me around one and a half days to complete the setup. We were a team of three developers, and after configuring, we created user credentials and began development.

The main costs in Snowflake come from computing and storage. If you allocate more storage but store less data with minimal usage, you can opt for a smaller database size, such as extra small, to save costs. Computing costs depend on how long processes or queries run. You can manage optimization and performance tuning to reduce costs. For example, if a process is scheduled to run every hour, but data refreshes only twice a day, you can adjust the schedule accordingly. You only run jobs when needed, reducing computing time and overall cost.

In short, you can control costs by managing storage and optimizing query performance based on actual data usage. Multiple factors, such as query timing and data refresh rates, play a role in minimizing expenses.

If you're using a service like Redshift, the pricing would likely be comparable to Snowflake. With Snowflake, you're paying for the service and the underlying cloud infrastructure since these are separate costs. Snowflake operates as a software package that must be installed on a cloud platform like Azure, GCP, or AWS, meaning you also need to use their computing, clustering, and storage services. This makes the total cost dependent on both Snowflake and the cloud provider.

Snowflake offers extensive features with a data warehouse background, including full SQL support and compatibility with T-SQL; other systems, like Redshift, also provide many similar features. That said, Snowflake has continued to grow in functionality and market appeal, making it more widespread. To thoroughly compare the two, you must look closely at the latest features Redshift has added, as it may offer comparable capabilities depending on your requirements.

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