I rate the overall solution an eight out of ten. I'd recommend Amazon Redshift. It's stable and scalable, needing little maintenance. It handles data well and provides fast reporting results.

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.

If it fits the bill and the business purpose, I would recommend using the solution. But when it comes to business needs, that's when all these things matter. Whether one tool versus the other supports all the business needs and meets the SLA and RT, or whatnot, then we are talking about different products. So it's based on business needs. 

Overall, I would rate Amazon Redshift a six out of ten. They still need to adapt the maturity and be on par with the open source community and ecosystem. Recent technology adoption is towards Delta. Microsoft is moving towards Delta. A lot of ecosystems are moving towards Delta, but Amazon Redshift is not making its move towards this technology, which is serving the engine. So that aspect has to grow.  So, there are a lot of aspects where they can improve.

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.

From time to time, the solution needs to be restarted for maintenance. I recommend BigQuery over Amazon Redshift. I don't have experience with Snowflake, but it's set to be more feature-rich than BigQuery or HSA. I was more happy using BigQuery. Redshift is doing what it's expected to do, but you had to invest in learning the setup. Overall, I rate the solution a seven out of ten.

I would rate it a five out of ten. 

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

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.

I would rate Amazon Redshift a nine out of ten. I am very satisfied with it.

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.

I would recommend it. However, I think we need to consider other configuration levels. You need to decide, and I would not go with the first option.

To evaluate the data you are planning to migrate, we need to assess the environment. What is the value of your data, and what type of data is it? The density of the data is also important. Before implementing Redshift, we need to ensure that the AWS configuration is activated. After that, you need to set up enrollment and increase your storage. I don't recommend making a purchase on the same day, but it is a critical moment at a high level.

I suggest purchasing a renewal that meets the deposit requirements so that you can have a good experience and optimal performance. You can increase the budget for the building process. If you have the right team, such as those with experience in AWS or those who are learning about Azure databases, they can start using Redshift without any issues.

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

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.

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 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 have only just started using Redshift, but we are not really satisfied with it.

I would rate this solution a six out of ten.

I would rate this solution 6 out of 10. 

If an organization has invested heavily in AWS services and they have a good knowledge of the AWS ecosystem, then I would recommend Redshift. Otherwise, I would still recommend Snowflake because Snowflake works very well with AWS services. I can have my AWS S3 buckets in which I can store my enterprise data lake, and then Snowflake works with that seamlessly. If the organization has good knowledge of AWS and good knowledge of RDBMS data warehouses, then we can recommend Redshift to them.

It all depends on how much investment that organization has done in Redshift. For example, we have a customer which has a very large setup. It's a large US-based company, where they have invested heavily in AWS. They're an AWS house, so they like everything about AWS. For them, we have recommended Redshift so that the overall tech ecosystem remains optimum. 

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.

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 rate the solution as an eight out of ten.

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 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 rate Amazon Redshift a seven out of ten.

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

You need to design the database structure with best sort and distribution keys, along with primary and foreign keys.

I would recommend this solution depending on the scale. You need to decide whether you want to be lined up with a single cloud provider or go over the service and have it deployed on multi cloud. There are many factors to take into consideration. 

I rate this solution seven out of 10. 

We usually rely on some distribution, not like classic Hadoop. We do not use  open source Hadoop because our customers prefer some distribution to get support. Some paid features from Cloudera and Amazon provide their own support.

We provide expertise for different services of AWS, e.g. most of them because we are a premium partner and we have program competencies. We develop data, big data, machine learning, and migration, so we cover a large field.

We have some clients with Azure, but most of our clients are with AWS.

The deployment of Amazon Redshift is through AWS. It's a home-based, proprietary solution. It's fully managed by AWS.

Amazon Redshift has implemented most of the features that we currently need, so I can't name additional features that I expect from them in the next release.

The number of people needed for the deployment and maintenance of this solution in our organization is just one: only to set up. It's just one DevOps.

I would recommend Amazon Redshift as a solution for others who are thinking about using it.

I'm rating Amazon Redshift an eight out of ten.

We're customers and end-users.

While I cannot speak to the exact version number, my understanding is that we are using the most up-to-date version of the solution. 

I'd advise those considering the solution to go for AWS products. They are the best. You will have more synergy between your software. It's nice not having multi-software working on the technology itself. If you can, use as many genuine Amazon products as possible and integrate them together. 

Overall, I would rate the product at a seven out of ten. 

If a company is already using Amazon Cloud or they're looking for a cloud solution, Amazon is one of the oldest and most reliable cloud service providers and Redshift is a no-brainer for data warehouse needs.

I rate this product a nine out of 10. 

I am just the user and we make use of the solution.

The solution is deployed solely on the cloud.

I believe there are around 20 people making use of the solution in our environment.

While the solution is not appropriate for every case in which usage must be evaluated, it can be used for sure.

I rate Amazon Redshift as an eight out of ten.

My advice for anybody who is implementing Redshift is to ensure that the requirements include having technical people on board to continuously work on getting the results you want. Because it's not that user-friendly, there is a need for a technical resource in the company.

Also, I would suggest watching out for scalability beyond what we have tested. If there is a need for scaling then it should be tested, although it depends on the use case.

If Redshift had a proper interface then I would score it higher.

I would rate this solution a seven out of ten.

Plan out your our DB design in advance and test your theories on running a small instance first. Use a good ETL tool, like Talend, so updates can be scheduled easily. Don't try to write these from scratch. Redshift has been a great DB for us to date. We haven't seen any slowdowns or outages!

I would recommend Amazon Redshift as it is part of the AWS platform and they are the biggest in the world.

I would give Amazon Redshift a rating of eight on a scale of ten.

I recommended it for data storage. I don't recommend integrated solutions, like Pacemaker unless you have an advanced team to handle it. I like using it, but it's too expensive. So, I rate the overall solution a seven out of ten.

In summary, this is a good solution and I recommend it. That said, the customer support needs to be improved.

I would rate this solution a seven out of ten.

With the most recent update, we should now be able to decouple storage from processes.

My advice for anybody who is implementing Redshift is to make sure that they are using it for what it is made to do. It's an analytical database, so it's not meant to process transactional data. It's the perfect tool if you use it for the right purpose.

Overall, it is a very stable and robust product. That said, there is still plenty of potential for improvement.

I would rate this solution a seven out of ten.

I would rate it a ten out of ten. 

I am interested in seeing a split between compute and storage, which is something that they are currently working on. We plan to start leveraging it at some point in the future.

In summary, I think that Amazon Redshift is a very good data warehouse and we really like it a lot.

I would rate this solution an eight out of ten.

Use this product for huge data mapping or aggregation. Use Redshift through VPC to keep their data very secure and for a long time.

If you evaluate Redshift, chances are that you should evaluate BigQuery too. So take the time to weigh the pro and cons of each (plenty has been written online about that).

Take a look at the reserved instances pricing. It is very advantageous if you know you will stick with Redshift for some time.

Take the time to learn PostgreSQL (eg: https://www.pgexercises.com/). Redshift, while based on PostgreSQL 8.0, supports a good number of advanced Postgres features.

Do not be afraid of joins. PostgreSQL is performs very well in this regard.
If you need performance, have a look at the suggested optimizations in the official documentation (such as setting up the correct distkeys, sortkeys and compression schemes).

Understand that Redshift has no indexes.

Understand that Redshift is an analytical database with columnar storage, and that it does not enforce constraints.

Redshift plays very well with a PostgreSQL instance in RDS linked to it via DBLINK (see this guide: https://aws.amazon.com/blogs/big-data/join-amazon-redshift-and-amazon-rds-postgresql-with-dblink/). I've used this in production at my current company, and this is tremendously useful. You can have your raw data in Redshift and aggregate it directly into RDS. To do this, insert into RDS what you select from Redshift through the dblink.

You need to make sure that the space used in DWH has to be a maximum of 50% of the total space.

You must create processes to vacuum and analyze tables frequently. Also, before creating the tables, you should choose the right encoding, DISTKEY and sort keys.

As of now, Redshift is far better than the other products in the market.

Lastly, I would like to mention that Redshift is more about scaling and stabilizing your data. One should also focus on data modeling from time to time.

I rate Amazon Redshift an eight out of ten.

Redshift is based on PostgreSQL and adds MPP/columnar features to make it a data warehouse product. It is very easy for developers to adopt this solution. Your existing team can easily work on Redshift with no extra cost of learning.

Be careful with vendor lock-in! You cannot move your Redshift environment to a different cloud provider or to an on-premise solution.

My rating would be 8.5. This a great product, but one still needs to know how to manage clusters and nodes.

In order to make your DB scalable and reliable. it has the greatest benefit of build on PostgreSQL, so any data specialist that has SQL experience can handle Redshift.

On a scale of 1 - 10, where 1 is the worst and 10 is the best, I'd give it an 8.

My advice to other is to prototype, prototype, prototype! Everything depends on your data and what you need to do to it. No two projects are the same.

Redshift, like any other big data technology, isn’t a silver bullet for everything. The most important thing is to understand your data and your requirements before you make any decision to use any technology.

I am very happy with what RedShift has. So far, anything that I have required has been there and whatever use case I have faced, the functionality is available.

My advice for anybody who is implementing this solution is to look into what certifications are available and which ones are required for different roles. Depending on the job, different certifications are relevant or required. For example, as a business analyst, a coding certification would not be useful for me and it would be a waste of money. These things should all be considered before beginning with any certifications.

I would rate this solution a nine out of ten.

It is very important to understand how Redshift is designed to work. The database schema design is not trivial and requires an in-depth knowledge about it, especially if your use-case requires it to perform well.

I rate Redshift nine out of 10. If you're thinking about implementing Redshift, I would recommend focusing on the use case. It's a warehouse database, not a transactional system, so they need to plan their workload before migrating to Redshift.

The suitability of this solution depends on the environment and the requirements. For some, Amazon Redshift is perfect. However, some people will need better queries. Based on my research, many of the products are pretty close. It is possible that the much higher priced solutions have more differences.

This is a good solution but the queries need to perform better.

I would rate this solution a seven out of ten.

We use public and hybrid cloud deployment models. We are Amazon partners.

The solution itself is very popular. Many people use it these days.

I recently went to an AWS summit in Zurich. I was very impressed by AWS and the presentation. Their solutions are very good.

I'd rate this solution eight out of ten.