What advice do you have for others considering AWS Database Migration Service?

On a scale of five, I would rate the recommendation level at four. Overall, I would rate the solution at eight out of ten.

Key features of DMS that are effective for large-scale migrations include the continuous data replication capability, which minimizes downtime, and support for heterogeneous database migrations. Additionally, it allows for multi-threaded processing and provides monitoring capabilities, making it easier to manage the migration process. The monitoring capabilities are robust, providing detailed logs and metrics through CloudWatch. It allows me to track the status of migration tasks in real time, assess performance, and quickly identify and resolve any issues that arise during the migration process. I encountered a data conversion issue related to changing time formats from UTC to a different format. By leveraging the transformation feature within DMS, I successfully converted the data to meet the customer's requirements. I ensure that sensitive data is encrypted in transit and at rest using AWS Key Management Service (KMS). Additionally, I conduct thorough assessments of access controls and compliance requirements specific to the client's industry. I stay updated with the latest features and enhancements related to AWS services by regularly attending webinars, participating in AWS training sessions, and following industry publications. Engaging with the AWS community through forums and conferences provides valuable insights and updates. Overall, I rate the product a nine out of ten.

Overall, my experience with AWS DMS setup and operation in a cloud environment has been positive and straightforward. I recommend AWS DMS primarily for enterprises, although it can be used by any company that leverages AWS databases. I haven't integrated DMS with AI tools personally, but theoretically, it supports data layer integration well for running AI algorithms on migrated data. I'd rate AWS DMS a nine out of ten for its efficiency in data migration and replication tasks and definitely recommend AWS DMS for users needing robust data migration capabilities within AWS environments.

The data replication feature of the solution has aided in minimizing downtime. For example, if our company is working with a large database at the customer's end, me and my peers need to use a continuous replication approach to minimize the time and decrease the amount of data left to be migrated during cut over. AWS Database Migration Service has impacted operational costs and efficiency in our organization in a positive way. For instance, the Schema Conversion Tool helps us in our company to covert the convertible objects and define the non-convertible objects in the targeted platform. AWS Database Migration Service allows manual effort to be calculated for transforming non-convertible objects and adopting target infrastructure. Some features of the solution belonging to the source systems are not supported in the target system, like the SQL language patterns; in such a scenario, the Schema Conversion Tool is used. I would rate the solution as eight out of ten.

We've been using AWS for a long time, including for non-Oracle services, and overall, we're very happy. It's much better than GoldenGate, which was a headache for us. Overall, I would rate the solution an eight out of ten.

I would rate the solution a seven out of ten. I would definitely recommend this product to others.

It could be a starting point for you, and if someone wants to use Oracle GoldenGate or another service, they need to purchase infrastructure. With AWS DMS, it's a matter of creating an account and starting from there. If you want to start, you could probably decide in the morning and by evening, you would have a DMS running on your AWS account. Overall, I rate the solution a seven out of ten.

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

I recommend using the solution if the end goal is AWS. It should not be used for GCPRs and on-premise migration. A lot of the features are applied while the migration tool is in place. The migration tools, like data and schema migration tools, make more sense if the target infrastructure is AWS. You could not use it as a separate tool. If someone is looking at an AWS infrastructure, they have to use the product. However, if they are not looking at AWS and want to use it as a tool, they should not use it. For such cases, they can use the available free and open-source versions of the tools. Whatever features are there in my system are all available in the solution. Out-of-box migration is also available. I don't see anything that is missing. My system is a real-time system. For me, it's a relational database with straightforward data structures. The volume is much higher if someone has big data processing migration, which may be a problem. For any big data solution, they will have to rework it. The product will not support it. When you have properly structured data, it is not that difficult for AWS to make it. I don't know how effective it will be if you have unstructured data, like big data and unstructured datasets. I have not seen a lot of use cases. Overall, I rate the product an eight out of ten.

We would rate this solution a 10 out of 10.

I'd recommend the solution to others. I'd rate the product eight out of ten.

AWS Database Migration Service is most useful for a company that is trying to do partial applications for a short amount of time until the entire application is cut over from one place to another. If you are considering AWS Database Migration as a solution for your organization, I recommend you pay attention to your CDC throughput, it is a single showstopper if you misuse it. I try to use it for our current application's traffic, which is about 30 megabytes per second. DMS would not be able to handle that in-house, it would just keep lagging. Overall, I would rate AWS Database Migration Service a nine out of ten. It is a very useful product.

Our infrastructure is fully on Amazon, so for us AWS DMS was an obvious choice to perform our migration as it is an additional service that Amazon provides. To those who are thinking of using the same, I would say go ahead and try it. If you come across any problems or have questions, you will most likely need to contact Amazon support, which can give good service, but it's not ideal. The paid support, however, worked well for us. I would rate AWS Database Migration Service a seven out of ten.

We are AWS partners. I'm not sure which version of the solution we're using. Whether it's the right product for everybody varies from situation to situation. There is not a generic thing you can say about the service or the situation. Everyone's experience will vary depending on their requirements. That said, in general, I would recommend it to others. Overall, I'd rate the product seven out of ten. There were challenges. And if the preassessment is there, we should have been warned in the preassessment about the challenges. If we fixed the issues in preassessment, we wouldn't have been waiting for hours and days for a job to complete. Considering it's a huge database, it's really difficult to wait on the whole thing over very small issues.

AWS Database Migration Service has two users within my company. It's me and another person, though that other person doesn't use the solution as much. I only use AWS Database Migration Service whenever data migration is required. I'm rating AWS Database Migration Service eight out of ten. My company has a partnership with AWS Database Migration Service.

My advice to others is for them to take the training first. If you don't take the training, it's a bit difficult to understand how it works. I rate AWS Database Migration Service a seven out of ten.

Overall, I would rate AWS Database Migration Service an eight out of 10.

Anyone considering AWS Database Migration Service should have some basic knowledge and know their use case. Also, they should understand that AWS will have many features available, but to commit to a database you need to have knowledge of how they build it. For example, if you are building an application with a login page, the details should be saved into tables, and you will need to know how to connect those tables. I would rate Database Migration Service a nine out of 10 overall.

We are a user of the product. I recommend the solution. I'm pretty happy with the capabilities. I'd rate the solution a nine out of ten.

I use a lot of Qlik Attunity and AWS Database Migration Service. I'm more of a consultant/engineer, so I use Database Migration Services to move data across different instances from on-premises to AWS, etc. My advice to people who want to implement the solution is that there are alternate products. AWS Database Migration Service is still a good start, but an alternate product such as Qlik Attunity does a very good job, e.g. Attunity gives you more control. I'm giving AWS Database Migration Service a six out of ten rating.

I rate AWS Database Migration Service six out of 10. However, if you are considering it, you should get a good idea of what you need. It's useful for some jobs, but you need to know how to use this better.

AWS is the leading provider of cloud services. It has extensive experience in this kind of scenario. The other cloud providers need to improve their tools and their licensing procedures. In this case, the licensing procedures are very complex for migration scenarios. On a scale from one to ten, I would give AWS Database Migration Service a seven.

I have not explored other solutions like GCP or Azure, but I have used the AWS side. On a scale of one to ten, I would give AWS Database Migration a seven. This score is because of a few difficulties I faced when setting it up. Because I worked on different applications on a couple of projects, I cannot completely make use of the AWS database. Maybe that is a developer mistake or something. That's the reason I am rating it a seven for now.

It is a good program and I will give it an eight out of ten rating. I would like to see more migration options in the next release.

I'm a consultant. We use the public cloud deployment model. I'd rate the solution seven out of ten.

We are using the public cloud deployment model. I would rate the solution eight out of ten.