Amazon Redshift Reviews

The solution is used to handle unstructured data.

We have been using the product for some time. We are exploring and learning from the new offering of the product.

AWS provides an ecosystem of different offerings. The product offers good support for the data lake. It also provides a lambda function for automating flows.

The initial deployment was complex.

I have been using the solution for a year and a half.

We have an SLA of 99.99%. The product is available most of the time. The vendor maintains the SLA well. They also have a scheduled maintenance window.

The tool’s scalability is pretty good. I rate the scalability an eight out of ten.

The initial support for moving to a serverless database was very good. AWS provides good support. The technical support is not consistent, though.

We need a solution architect from AWS to help us with deployment.

Initially, we saw a return on investment. Now, the cost is going up according to our use cases. We need to optimize the cost.

The cost must be improved. We’re concerned about the cost. It’s driving a lot of TCO for us. We are looking for alternatives to optimize the cost.

Nutanix also provides similar products. It also offers different options for cloud providers.

It’s a pretty good solution. We plan small and grow big over time. Overall, I rate the product an eight out of ten.

We use it for data warehousing. Currently, I'm setting up a data link with Redshift to fetch data from our data lake.

The most valuable feature of Redshift is its cluster.

Redshift's serverless technology needs to improve because not everyone is technically inclined. Organizations want to quickly access and import data into their data warehouse without hassle.

Redshift's ETL tool, Glue, is not seamlessly integrated with Redshift. I've encountered many instances where it couldn't fetch the perfect data type from the source, which should be intuitive. Snowflake's ETL tool, on the other hand, is more intuitive and seamless.

I have been using this solution for two years. I am working with the latest version.

I haven't faced any stability issues because when it works, it runs continuously.

The initial setup is a complex process, especially for someone who is not familiar with nodes and configuring terms like RPUs. You need to consult the documentation to understand what an RPU is.

Moreover, Redshift can be difficult to maintain, especially the Redshift cluster instance.

When it comes to the initial deployment and implementation process of Redshift, there are two types of nodes to choose from: DC2 and RA3, which are for different requirements based on the load. One is for storage, one is for storage and checking, and one is for the computing center.

First, the user needs to know their exact requirement, unlike Snowflake, which automatically scales up and down based on the requirement using the Retrieval Service tool.

The service has not matured yet, and for the Redshift cluster, scaling has to be done manually. The cluster also needs to be set up manually, which is not ideal, especially when Snowflake is already in the market.

It is easy to deploy if you already know how to use Redshift. But if I were a new customer, I might need assistance.

Redshift is a bit less costly than Snowflake, but the effort justifies the cost for Snowflake.

I would suggest starting with a three-cluster that is DC two large, especially if you are setting up a cluster-based search. We offer a three-month or one-month trial, which will allow you to see if you can handle the manual scaling up, scaling down, and maintenance of Redshift. If not, then you can switch to a serverless data solution.

Overall, I would rate it a seven out of ten.

I have used DBeaver to connect to SAP Amazon Redshift and my main use case is for SQL. I map data from a graph database into SQL.

Amazon Redshift has benefited the company by allowing us to scale. 

The solution could improve in handling more data formats and more native support for RDF.

I have been using Amazon Redshift for approximately one and a half years.

The stability of Amazon Redshift is good.

Amazon Redshift is a scalability solution.

I have not used technical support. If I need support I ask my colleagues.

The initial implementation of Amazon Redshift is simple. There was not anything difficult about getting started with the solution.

It's important to have a grasp of the environment you're working in, including a basic understanding of Amazon AWS. Additionally, when selecting an interface to work with, it's essential to choose wisely, as you'll likely be using it for an extended period of time.

I rate Amazon Redshift an eight out of ten.

We use this solution for production and customer data for one of the lines of the business, which is basically one of the warehouses. I oversee the whole architecture infrastructure.

The price isn't bad for the performance for a cloud data warehouse. It's also connected to Databricks but uses SQL. It's comparable to BigQuery. If the analyst knows SQL, which is comfortable and easy to use to go between all of these tool stacks, I think it's reliable. It's a secure and reliable data warehouse.

The performance is good, and it's pretty fast. We also have Looker and MOLE connected to it for visualization, which works seamlessly. We're storing a lot of data. There's a lot of transactional data, clickstream data, and telemetry about the customer, what they're purchasing, call logs, and marketing data.

The analysts are familiar with SQL, and they're able to do this. Even the data scientists who aren't that savvy in Python, because they are very strong in SQL, are able to interact with it very quickly. I'm able to bring in more analysts for support.

There are physically too many pipelines for a company of this size to maintain. For a data scientist, it's very difficult to learn the data in all of these different environments. It's easier to train people in just one environment to start with, like Snowflake or Databricks. It's difficult to have so many technologies that are very comparable, and each comes with a price tag.

I have used this solution for seven months in my current company, but I have also used it in a couple of my previous companies.

The stability is good. For a mid-size company, it's very stable.

It's very scalable.

I would rate the technical support as 10 out of 10.

We had one or two tickets, and they responded extremely quickly. Technical support is good, but that's because we aren't running into many issues. The solution is pretty stable. The individuals who set it up did a very good job.

It wasn't too complex because only a few people were needed to set up the solution.

It's not very pricey compared to other tools. I would rate the price as 5 out of 10.

In my organization, we also use GCP, Amazon EC2, Databricks, and Snowflake. We also have Delta Lakehouse. I'm going to move everything into the Delta Lakehouse. For a company of this size, it's a lot of tools to physically maintain with a small data engineering team.

I think Snowflake has a few more features. In Redshift, you need to write a bit more SQL in some instances, but it's very user-friendly and fast. It can be used as a data warehouse solution as well. It can also do some analytics.

Redshift is comparable to other solutions. I wanted to go with Amazon EC2 because we also have Databricks, and I think I can cover some of those features with the combination of that.

I would rate this solution as eight out of ten. It's a very strong solution.

My advice is to do your research and see if it makes sense for you. You can always request a demo from Redshift.

I use the solution in my company for our data warehouse and databases.

The high price of the product is an area of concern where improvements are required.

I have been using Amazon Redshift for three years.

My company uses IBM Cognos as a reporting portal on top of Amazon Redshift.

My company moved from Netezza to Amazon Redshift since the latter is available on the cloud platform. My company used some migration tools to shift from Netezza to Amazon Redshift, and it took almost a year.

Amazon Redshift was not helpful in improving our organization's functioning, and I believe that previously, we had a better database named Netezza in place.

It is an expensive product.

The tool can handle some large-scale datasets for our company since we use data shares.

I am satisfied with the performance of the product.

The product is able to fulfill my company's needs associated with data analytics.

Amazon Redshift is used as a storage tool.

I rate the tool a seven out of ten.

We use the solution for data storage of reports.

Redshift Spectrum is the most valuable feature.

The product must become a bit more serverless. Users should have to pay only for the resources they consume.

I have been using the solution for one year.

The tool is quite stable.

Around 20 people in our organization use the product. The tool’s scalability is good.

The solution is deployed on the cloud. The initial setup was pretty easy.

The product is quite expensive.

We also tried using Athena. However, Redshift was faster.

We use the tool because we have everything on AWS. Amazon Redshift is best for fast reporting. People who want to use the solution must try using Athena. If it is not fast enough, they can try Redshift. Overall, I rate the product an eight out of ten.

We use Amazon Redshift for our data warehouse to store a lot of our data for a client.

The most valuable feature of Amazon Redshift is its ability to handle really large sets of data. In our case, the solution does a lot of things that would be difficult to do otherwise.

Amazon Redshift is a little more expensive than other products.

I have been using Amazon Redshift for four years.

Amazon Redshift is super stable, and we haven't faced any outages or other issues.

The solution's scalability has been fine regarding how much data we can load into it. Once the solution is set up, we pay for what we use. Three people are using the solution in our organization.

Users should select Amazon Redshift depending on what their needs are. Amazon has other cheaper database products, but Amazon Redshift is a really good option for users who need a lot of computation.

Overall, I rate Amazon Redshift ten out of ten.

We use Redshift Spectrum for creating temp tables during the Ignition process.

I have primarily used the Redshift Spectrum feature and found it most valuable.

During our last office project, Redshift couldn't perform well even for a data size of 6 TB. Thus, compared to Teradata and Snowflake, the solution needs to work faster. They should extend the plan by including better optimization and readability as we get while using Teradata. Also, they should provide zero-copy coding and sharing facilities.

I have been using the solution for three months.

I rate the solution's stability as a seven.

There is no issue with the solution's scalability.

The setup was straightforward as I have a POC. It was a simple process.

The solution is available at a mid-range price as compared to other vendors.

While using Redshift, we need to combine it with Glue to complete the process. Whereas, Databrix offers the same procedure without combining two solutions. Redshift would work well with small businesses if they already use AWS services. They can use Redshift if the database is not that huge. I recommend Snowflake over Redshift. I rate the performance as well as the overall product as a five.