Amazon Redshift Reviews

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.

It is scalable, easy to use, and has very good query performance. It is serverless as well.

They introduced machine learning directly in to Redshift, and you can now query using machine-learning functions.

It's very easy to migrate from other databases to Redshift. There are migration tools dedicated for this purpose, enabling migration from other databases like MS SQL directly to Redshift. The majority of the scripts will be automatically transposed.

AWS Snowflake has a very good feature for cloning databases. It makes it easy to clone a data warehouse, which is useful. I would like to see this feature in Redshift. 

We have been using Amazon Redshift from 2013.

For stability, I would give a rating of ten out of ten.

We have 16 Redshift users in our company, and I'd rate the scalability at ten out of ten. 

Redshift's technical support has been great.

The initial setup is simple.

In comparison to the price of similar solutions, Redshift's cost is the lowest.

I would recommend Amazon Redshift and would rate it at nine on a scale from one to ten, where one is the worst and ten is the best.

For the on-premises version of Amazon Redshift, we need to start from scratch. However, with the cloud version whenever you want to deploy, you can scale up, and down, and it has a data warehousing capability. Redshift has many features.

They have enriched and elaborate documentation that is helpful.

We are using third-party tools to integrate Amazon Redshift, they should create their own interface on their own for it to be easily connected on the AWS itself.

I have been using Amazon Redshift for one year.

Amazon Redshift is reliable and has high availability.

The scalability of Amazon Redshift is good.

We have approximately 20 people using this solution in my organization.

Before we were using Amazon Redshift, we were working with Postgres, Greenplum, and Oracle SQL. These were on-premises databases, and we migrated to the cloud.

The price of Amazon Redshift is reasonable because it depends on the usage that you use and for DWH for the long term.

I would advise others that if they have a large set of data where you have a less number of updates, then choose Amazon Redshift. If there is more update and fewer inserts, then do not use Amazon Redshift.

I rate Amazon Redshift an eight out of ten.

Redshift is a managed service for data warehouses.

I find the most valuable features to be the MPP style of processing, which mostly all of the data warehouses provide. The ability to integrate all other AWS services, such as NSS and S3, with little effort is very helpful. The service is well maintained, there are update patches frequently.

We recently moved from the DC2 cluster to the RA3 cluster, which is a different node type and we are finding some issues with the RA3 cluster regarding connection and processing. There is room for improvement in this area. We are in talks with AWS regarding the connection issues.

In an upcoming release, I would like to have a Snowflake-like feature where we can create another cluster in the same data warehouse, with the same data. You can create a different cluster and compute nodes for each of your use cases, for retail, and for your data analyst all while keeping your underlying data safe.

Additionally, the cluster resize process takes down the cluster for too long, approximately 15 minutes. There are limitations to the size, you can resize only by a multiplier of two, for example, if you have four nodes then you can either go to eight nodes or you can come down to two nodes. There should be fewer limitations.

I have been using Amazon Redshift for approximately one year.

There are three people in my organization using this soltuon.

Their technical support is good. They provide assistance when we need it but since we were experiencing a connection issue it was taking longer to get a resolution. We had to involve a vendor to get it resolved for us.

I have previously used ClickHouse.

The installation was easy.

The price of the solution is reasonable. According to the RA3 cluster particularly, it provides 128 GB of storage with only four nodes. If you can manage your computations processes with the help of materialized views and proper queries. I think the IP clusters are very useful and overall fair for the price.

We have been evaluating Snowflake and are in the POC phase. If it passes our quality tests then we will be moving to it soon.

I rate Amazon Redshift a seven out of ten.

We mainly use the solution for marketing analytics.

The solution works fast. I use Redshift to clear a lot of web page data. I use it mainly as an extraction tool to obtain the information I need for a project and store it in parquet files on a disk. Later, I work on the data using Python. I write back all my final results to Redshift and store the temporary files on a local machine.

They should provide a structured way to work with interim data than to store it in parquet files locally. Also, Redshift is unwieldy. There should be better integration between Python and Redshift. It could be more accessible without using so many sequels.

They should make writing and reading the data frames into and from Redshift easier. The performance could be better. I have used Redshift for extensive queries. For the large tables, it's easier to unload to Redshift, but subquery tables that run complex grids are slower for configuration. I have to use the unloaded command to unload the whole table. Further, I have to read the table into a server with extensive memory in Python and process the data ahead. It's not optimal. 

We have been using the solution for two years.

I rate the solution’s stability as a nine.

The solution is scalable. It handles different loads very well. We have 80-100 users using the solution in our company.

The setup was quite complicated. For instance, if you use AWS Glue to automate loads into Redshift, setting up the security for the requirements between the two is complex. I've struggled a lot to set up the cluster on VPC and to get all the endpoints set up correctly with the right access and services. Especially from Glue's endpoints, I had to repeat the same process every time. It consumes a lot of time. In comparison, the CloudOps executives do the setup very quickly.

I have heard complaints about the solution’s pricing, and thus I rate it as a five.

I rate the solution as an eight out of ten.

We use Amazon Redshift as our data warehouse.

I found the Amazon Redshift computing services easy. I found the computing instances the most incredible in the solution.

What would make Amazon Redshift better is improvising on the pricing structure. For example, Acronis provides backups in cybersecurity, yet the pricing is a bit lesser than Amazon Redshift. I was comparing AWS, Amazon Redshift, Azure, GCP, and Acronis, and I found that Acronis has a lesser price than the other solutions in the archiving space.

I have at least two months of familiarity with Amazon Redshift.

Amazon Redshift is a stable solution.

Amazon Redshift is a scalable solution that also suits enterprise companies.

I haven't contacted Amazon Redshift support because I'm not a client, but according to my subordinates, the support is excellent.

Amazon Redshift is very easy to deploy, and deployment-wise, it's impressive. It only takes two to three minutes max to deploy.

Pricing for Amazon Redshift is reasonable, though it could be somewhat higher than other solutions, such as Azure. Still, when you base your comparison on the services offered and the pricing, it's the most reasonable versus its competitors, such as RDS.

My company provides backup solutions.

I'm a business analyst with little expertise in a specific service or solution, but I've gone through all the solutions.

I have experience with Amazon Redshift.

What I'd tell others looking into implementing Amazon Redshift is that it's one of the market's best databases or data warehouses right now.

My rating for Amazon Redshift is nine out of ten.

I'm an Amazon partner.

I'm a freelancer/consultant, so I use the solution across a wide variety of contexts. 

The most valuable feature is that the solution is fully embedded in the AWS stack. 

The product is the best database for analytics, BI, and whatever else I encounter. 

The customer support could be more responsive. 

I've used Redshift for seven years. 

The solution is very stable. 

The tool is highly scalable. I'm a freelancer, so I use the solution in different contexts, but the total number of end users is usually between 100 and 200.

I contacted technical support before, and they could be more responsive. 

Positive

The initial setup was straightforward. I rate it five out of five here.

The product is cheap considering what it provides; I rate it five out of five for affordability. 

I rate Amazon Redshift ten out of ten. 

I recommend the solution to anyone in an AWS environment. I see a lot of fuss about Snowflake, and I used both, but I'm not much of an Azure guy. I don't know why the pickup rate for Redshift in NL is so low, but that's more marketing-driven, as Snowflake has very aggressive marketing.

Amazon Redshift is one of the best products I've ever come across.