Amazon Redshift Reviews

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.

We were using the solution for our data backup, but we wanted to optimize it, so we turned to AWS Glue. Amazon Redshift wasn't really great for us and wasn't working out.

Amazon Redshift was used for data storage while moving back from S3 to Amazon. However, it lagged, taking its own sweet time for data backups which also depended on the server location. Because of the aforementioned reasons, we started losing a lot of data that wasn't even real-time data. Ultimately, this affected our analytics at the end of the day. Also, we have been trying to do some work on our AI models, which emit out recommendations based on the live dataset. There were a lot of lagging issues. So, for example, sending out somewhere around 0.1 million or 100,000 emails used to take almost 12-14 working days, and this also includes the process of pulling all the data and sending them to CronJobs. Since we wanted all this work to happen in real-time, we had to get rid of the tool.

I would like Amazon Redshift to improve its performance, analytics, scalability, and stability. Other than these points, I am not aware of any other areas to address since Amazon provides a variety of independent services for their customers to choose from, and if one were to express dissatisfaction with Amazon Redshift, Amazon would likely suggest AWS Glue as an alternative. Similarly, if another issue arose, Amazon might recommend Amazon RDS. There are a lot of things they try to upsell to you, each with its own pros and cons and in different packages offering different perks. So, it all depends on your business needs and what you choose for your business. I wouldn't criticize Amazon for this because they have created packages tailored to their customer's needs, which helps to prevent customers from looking elsewhere.

I have been working with Amazon Redshift as an implementer for three years.

Stability-wise, it has a lot of issues with threats, and that is why we went for a threat shift optimization. In short, I mean to say that it is not stable at all.

If you require a highly scalable solution, I would not recommend Amazon Redshift. We currently have 12 clients using Amazon Redshift, and the scalability of the solution is terrible. In terms of scalability, I would rate this solution a three or four out of ten.

Amazon Redshift has a lot of documentation, but the setup is fine. Three years ago, the solution's deployment process took over a month or a month and a half.

Every solution has a cost and comes in different packages. Considering these factors, AWS Glue is on top. Though Amazon Redshift is good, it depends on what kind of business you're trying to do, what type of analytics you need, and how much data you have.

For Amazon Redshift, we pay around INR 60,000 annually. The cost factor also depends on the number of existing customers. In addition to the standard licensing fee paid for AWS, we incur a cloud storage cost of around a quarter million for the amount of data. We also have to bear additional costs for data security and cybersecurity, which are well taken care of by Amazon, hence the premium pricing. There are several other features and services provided by Amazon that justify the premium pricing.

Amazon Redshift is a horrible solution. I recommend my customer to use AWS Glue since while dealing globally with real-time data, which you need to make decisions, factors like how much cost and data is needed to make a decision should be considered. Apart from this, if customers are paying a huge price for the solution, then probably Amazon shouldn't mind spending on the tool. However, it may not be necessary for small businesses with only a few thousand data points. Although Azure is a better option, some clients prefer AWS, and we had to develop a solution using AWS for our client. Overall, I rate this solution a three or four out of ten.

I use Amazon Redshift for the creation of SQL ETL procedures in a business system. Business people check this in a front-end application, and it helps them plan sales for the next year.

Redshift is being deployed on a Microsoft Azure server.

There are about six people working on this project and using the solution, but there are many similar projects running on Oracle and Redshift.

I like it because the usage is very similar to Microsoft SQL server. The structure of the query and the temporary tables are very similar. Until recently, I thought it was the superior database, but now I think that Redshift is better.

The explain panel in the Redshift database could be better.

I have used this solution for 10 months.

The solution is stable. I haven't had any problems or downfall with the database in the 10 months that I have used the solution.

I have also used Microsoft SQL server and Oracle.

Setup was difficult because I had to set up 25 connections with different users and passwords. The connections have been predefined, but there were still problems when trying to connect for the first time. I had some problems with some certifications that were malfunctioning. This might have had something to do with the functionality of my keyboard because if I pushed a random combination on the keyboard, it would delete the certificate from the folder and the connection wouldn't work. I think this is a problem with the remote desktop rather than with Redshift.

I would rate this solution as eight out of ten. I can't give it a higher score because there are some issues with variable character columns in the table. Otherwise, it's a great database.

Some of my former colleagues from a previous job have joined my organization, and they have had some issues with the SQRs because some things work differently in Redshift, like the partition bar. If someone has issues with Redshift, my advice is to check with support.

We use Redshift as a central data warehouse. This data can be consumed directly by AWS services or different applications where we can provision the data via Athena. If we want to create more business intelligence tools and analysis, we write some SageMaker notebooks for deploying machine learning models based on the data.

We have a wide variety of use cases, but we generally use it to have one place where we can store data. We also connect enterprise legacy systems such as SAP systems. I'm mostly connecting shop floor assets and the industrial machinery to store relevant data in one place and make it available. Via Athena, combined data can then be retrieved with easy SQL queries.

Usually, we use the newest version of the solution. If there are new updates available, we try to take them directly.

Our customers usually have a hybrid cloud or full cloud architecture with minimum on-premises data centers.

We have five to ten customer projects per year in our department in which we set up data lake houses using Redshift. Those companies have between 3,000 and 15,000 people. Not everybody has to use Redshift. Depending on the project and the size of the consulted company, there are 2,000 to 3,000 end users who need access to the stored data.

We are a consultancy company of 1,500 people. Those who use a sophisticated data warehouse architecture tailored to the business requirements, profit a lot since this is the foundation of business intelligence which makes a company more resilient and adaptable to change. We try to select the correct service for our customers, and when using AWS, we usually do data warehousing with Redshift.

The main benefit is that our portal for end users is running in AWS, so we can easily connect it to other AWS services. The most important part for us is the connectivity inside AWS.

Pricing sometimes depends on the setup (key, etc.) which makes it hard for somebody new to AWS. Detailed research has to be conducted to end up with a competitive solution in terms of pricing and performance.

I have used Redshift for a year and a half.

I would rate the stability as nine out of ten since AWS provides a relatively resilient solution in general due to load balancing and auto scaling capabilities.

I would rate the scalability as ten out of ten.

We are a certified partner of AWS, so we have a different level of customer service, but usually, the customer service is fast and efficient even without a direct contact person.

Positive

My company has more than 20 years of experience with SAP in general and the Data Warehouse Cloud is also used for customer projects.

I'm familiar with AWS in general, so the setup is not difficult. For people who struggle with IAM or role-based management, the setup can be challenging.

In cases where there is deep knowledge of creating a microservices architecture using AWS, a project can be executed quite fast. The only reason for using AWS is the aim for AWS Redshift as a data warehouse, the setup is not as easy.

The amount of time it takes to deploy depends on the project. We try to do our projects incrementally, so we start with one department and deploy all of the relevant data from that. It takes about two to three months to draft a minimum viable product, connect a couple of machines, and use Redshift to work with data consumed by analysis tools or reporting capabilities. It is possible to set up a data warehouse in one or two weeks.

There are different types of projects, and if we do it within a waterfall approach, it can take a long time.

When creating a data warehouse using Redshift, we first analyze the current situation and then sketch the architecture in AWS with the required ETL process to ingest and consume data, including the right processing to aggregate and enrich data according to business requirements. This is where all the customization comes in.

For deployment and maintenance for only one customer, I would say that three to six experienced people can handle the job. For maintenance work, in my opinion, there is only one person required for two or three hours a week maximum.

I would rate the setup as eight out of ten.

The cost will depend on how you set up your warehouse and what kind of data you store. I would rate the pricing as six out of ten.

I would rate this solution as nine out of ten.

My advice is to use a consultant to set it up correctly and to get familiar with data warehousing in general. It's pretty straightforward once you're using the data management console. Anyone could use Google to set it up, but to do it correctly and sketch the perfect architecture, an external consultancy company should handle it because the usual IT departments aren't that experienced.

I think Redshift is worth the money, and there's always some return. Most companies don't have a full solution for business intelligence. AWS provides a pretty good service architecture to implement this. Anyone who uses Redshift or a data warehouse in general will have a return on investment.

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.

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.

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.

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.