Try our new research platform with insights from 80,000+ expert users
Consolador Daroy - PeerSpot reviewer
Development Team Manager/Chief Solutions Architect at a consultancy with 11-50 employees
Real User
Top 10
Replicate databases between AWS and Oracle, especially for backups and test environments
Pros and Cons
  • "For our simple requirement of migration, DMS is just a typical AWS RDS with an IPSec tunnel to Oracle. The most valuable features for us are the networking capabilities like VPCs and VPNs."
  • "The cost is a concern. We use DMS because of its simplicity, but the price could definitely be more competitive."

What is our primary use case?

We're currently moving our whole database from AWS to Oracle. We want to avoid interrupting production systems, so we're using DMS to continuously replicate data from the AWS RDS database to the Oracle database in OCI. Once we're sure all data is consistent, we'll switch over to Oracle and shut down the AWS database.

This should minimize downtime to about 15 minutes, and all our services in AWS then point to the Oracle database.

What is most valuable?

For our simple requirement of migration, DMS is just a typical AWS RDS with an IPSec tunnel to Oracle. The most valuable features for us are the networking capabilities like VPCs and VPNs.

Currently, we're happy with DMS because it's simple and meets our needs. We're still syncing the data, but once that's done, we'll cut off the AWS database. Compared to Oracle GoldenGate, DMS is definitely easier to use. We haven't encountered any major difficulties.

What needs improvement?

The cost is a concern. We use DMS because of its simplicity, but the price could definitely be more competitive.

So, in my opinion, some potential areas for improvement are price and possibly supporting Oracle Autonomous Database (ADB) on AWS, as it's a powerful option.

Oracle ADB on AWS would significantly reduce our migration workload. Price and lack of ADB support are the main downsides of DMS for us right now. In fact, about 60% of our monthly AWS costs go towards database services.

For how long have I used the solution?

We've been using DMS for a while to replicate databases between AWS and Oracle, mainly for backups and test environments.

Buyer's Guide
AWS Database Migration Service
March 2025
Learn what your peers think about AWS Database Migration Service. Get advice and tips from experienced pros sharing their opinions. Updated: March 2025.
844,944 professionals have used our research since 2012.

What do I think about the stability of the solution?

I would rate the stability a six out of ten. It took us a while to get it running smoothly. It wasn't entirely straightforward. But once it was set up, it was stable. AWS support was helpful during the initial setup.

What do I think about the scalability of the solution?

We haven't encountered any scalability issues so far. We might need to increase the database size later, but it's not a problem. So, I would rate it an eight out of ten.

How are customer service and support?

We actually bumped up our support level for extra coverage, and they've been very helpful. We also have AWS expertise on our team, so there haven't been many difficulties. Overall, the support is good.

The biggest challenge we faced was setting up the IPSec tunnel between the two private networks. It took a while to figure out why they weren't communicating even though the tunnel was up. Luckily, our AWS networking experts managed to fix the routing issue.

How would you rate customer service and support?

Neutral

Which solution did I use previously and why did I switch?

Currently, we're moving from AWS to Oracle. We're migrating our database, and that's already been taken care of. The issue with AWS has been addressed, and we no longer have any problems with it.

We're new to DMS. We decided to use it about three months ago. That's why we compared DMS with GoldenGate to choose the best option for migrating our database. 

How was the initial setup?

The setup process was simple enough for us because our database is plain and doesn't have many blocks. It's just a typical cloud-based product, like most AWS services.

Which other solutions did I evaluate?

We use the enterprise and the AWS license, which is a bit expensive. We're consolidating our databases from AWS to Oracle, which we find more cost-effective. So, we're using an autonomous database in Oracle, a feature not offered by AWS.

What other advice do I have?

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. 

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Ram-Krishnan - PeerSpot reviewer
Data engineer architect at Freelance
Real User
Top 5
Good for data migration for smaller workloads, but its scalability and performance could be improved
Pros and Cons
  • "AWS Database Migration Service is good for smaller workloads and provides compatibility."
  • "The solution’s scalability and performance could be improved."

What is our primary use case?

We were using the solution for the migration and replication of data.

What is most valuable?

AWS Database Migration Service is good for smaller workloads and provides compatibility.

What needs improvement?

The solution’s scalability and performance could be improved.

For how long have I used the solution?

I have been using AWS Database Migration Service since it came up.

What do I think about the scalability of the solution?

I rate the solution a six or seven out of ten for scalability.

How are customer service and support?

The solution’s technical support is good.

How would you rate customer service and support?

Neutral

How was the initial setup?

The solution’s initial setup is easy.

What's my experience with pricing, setup cost, and licensing?

The solution’s pricing is reasonable.

What other advice do I have?

AWS Database Migration Service is a cloud-based solution.

Overall, I rate AWS Database Migration Service a six or seven out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
AWS Database Migration Service
March 2025
Learn what your peers think about AWS Database Migration Service. Get advice and tips from experienced pros sharing their opinions. Updated: March 2025.
844,944 professionals have used our research since 2012.
Senior Cloud Admin at Brillio
Real User
A comprehensive data migration solution that integrates easily with all ETL tools
Pros and Cons
  • "We particularly like that this solution has the facility to integrate with all ETL tools."
  • "We would like to see some improvement in the performance of large scale procedures, such as when we migrate from Oracle to csSQL."

What is our primary use case?

We use this solution to enable us to carry out heavy, data-level migrations across multiple ETL tools.

What is most valuable?

We particularly like that this solution has the facility to integrate with all ETL tools.

We also like that this solution provides us with high speed velocity, performance, scalability, and throughput for our data migration tasks.

What needs improvement?

We would like to see some improvement in the performance of large scale procedures, such as when we migrate from Oracle to csSQL.

For how long have I used the solution?

We have been working with this solution for over five years.

What other advice do I have?

We would rate this solution a 10 out of 10.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Software Engineer at a financial services firm with 10,001+ employees
Real User
Stable, has a straightforward setup, and works even in terabyte-scale migrations
Pros and Cons
  • "What I like about AWS Database Migration Service is that it's a good product that allows you to migrate terabytes of data. My team was able to migrate almost 16TB of data using AWS Database Migration Service. The solution works fine for my use case."
  • "What needs improvement in AWS Database Migration Service is that it lacks a log file validation feature. If the solution could provide more details about a particular transaction, that would be helpful. The stability of AWS Database Migration Service for online CDC records also needs to be improved."

What is our primary use case?

I'm using AWS Database Migration Service for migrating data from an on-premise Oracle database to a database on AWS.

What is most valuable?

What I like about AWS Database Migration Service is that it's a good product that allows you to migrate terabytes of data. My team was able to migrate almost 16TB of data using AWS Database Migration Service. The solution works fine for my use case.

What needs improvement?

What needs improvement in AWS Database Migration Service is that it lacks a log file validation feature. If the solution could provide more details about a particular transaction, that would be helpful.

The stability of AWS Database Migration Service for online CDC records also needs to be improved.

For how long have I used the solution?

I've been using AWS Database Migration Service for more than six months now.

What do I think about the stability of the solution?

AWS Database Migration Service is not as stable for large volumes of data, especially when you process CDC records daily.

What do I think about the scalability of the solution?

AWS Database Migration Service is a scalable solution.

How are customer service and support?

In terms of the technical support provided for AWS Database Migration Service, seventy percent of the team is knowledgeable, and the remaining thirty percent isn't as knowledgeable.

Sometimes, the response from support is very slow, and for every question, you'll get the same kind of answers. The technical support team should analyze the errors properly, especially with production and queue errors because I don't see that happening currently.

How was the initial setup?

AWS Database Migration Service has a straightforward setup. On a scale of one to five, I'm rating the initial setup four out of five.

What's my experience with pricing, setup cost, and licensing?

I'm not aware of the pricing for AWS Database Migration Service.

What other advice do I have?

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.

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
PeerSpot user
reviewer2130081 - PeerSpot reviewer
Software architect at a computer software company with 51-200 employees
Real User
Top 20
A stable and scalable product that provides real-time synchronization of on-premise database to plan releases
Pros and Cons
  • "The database migration services allow us to do real-time synchronization of on-premise and database to plan out our releases."
  • "The product's performance could be a little bit better."

What is our primary use case?

The tool is offered as part of AWS stacks. We use it for data migrations from on-premise to AWS stack via PostgreSQL and MySQL. We also use it for the infrastructure configuration to simplify the setup because we are going on RDS. The AWS platform will manage everything. We use it for the simplification of migration. We do not do a lot of study on how exactly to map the database provisioning.

What is most valuable?

The database migration services allow us to do real-time synchronization of on-premise and database to plan out our releases. We do prod testing to keep the prod data in sync, at the same time, not expose it much. The automation of this synchronization helps us ensure the data is consistent in both AWS and on-prem. Then we can switch over wherever you need it. Parallely, we can do production performance testing and user experience testing without actually writing a lot of code. It comes out of the box. It is one feature that we like a lot.

The other feature I like is schema migration. When we want to upgrade it to MySQL, we can easily upgrade it. It is another stack. We haven’t used database migration. We can use it if we want to move from Oracle to PostgreSQL. It also comes as an out-of-the-box solution. I think these three things are very good. However, we have not used database migration yet because we do not plan to install software yet. The solution has a good feature stack.

What needs improvement?

The product's performance could be a little bit better. It is good in terms of the data, but it is difficult for the first time. After that, the synchronization is fine. We saw a few failures because of the bandwidth the first time the data got loaded. The performance could be better, but it's only for the first time. We haven't seen any performance-related issues post the initial setup.

For how long have I used the solution?

I am using the solution right now.

What do I think about the stability of the solution?

There's no issue with stability. The solution is quite stable. It has to be stable. The only reason we are moving to AWS is to be scalable and perform well.

What do I think about the scalability of the solution?

On-premises scalability is the reason why we are moving into AWS. The product's purpose is to introduce scalability. We would not have picked it up if it was not a ten out of ten. It is expected to be scalable because of how the nodes are getting set up in AWS. We have a medium to large user group. It's for a finance-related project. So there are quite a bit of end users, but not very high. It is targeted at brokers and stock traders.

How are customer service and support?

The technical support is really good. We have partnered with Amazon, and we are part of Amazon's consultation team. There's a service engineer and an overall account manager who take care of the issues. For any automation issues, we can go through them to coordinate. They provide excellent support.

How would you rate customer service and support?

Positive

How was the initial setup?

The initial setup is quite easy. The product has one of the easiest installation setups.

What about the implementation team?

My team, who has expertise in Data Migration Services, did the implementation in a few hours. We have five DevOps team members, two architects, one for data and one for infra and application, and managers. The development team varies. It depends on the system. The rest is the core team. Below the core team, we usually have pilot teams and project teams. We might have a specific development team if a feature enhancement needs to happen, but it is very rare. The core team comprises five DevOps, two architects, and one manager. The maintenance team takes over the maintenance of the on-premise system.

What other advice do I have?

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.

Which deployment model are you using for this solution?

On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer: Integrator
PeerSpot user
Principal engineer at a tech vendor with 10,001+ employees
Real User
Supports a smooth migration
Pros and Cons
  • "The solution is instantaneous. We can launch the service and reduce the end number of manpower."
  • "Whatever solution worked today can not be reused in the next migration."

What is our primary use case?

We have a database team that supports migrations to public, private, and hybrid clouds depending on the client's needs.

What is most valuable?

Prior to the migration, during the earlier stages, we had a lot of problems. SCT is a migration tool provided by Amazon that helps us to convert the schema. 

We have an in-built tool provided by Amazon. It is a database migration tool that supports a smooth migration. The solution is instantaneous. We can launch the service and reduce the end number of manpower.

What needs improvement?

Our organization works with both client data migration and the cost governance part. Years ago, the price was nominal and acceptable for the client to do a migration. Now, prices are challenging, especially with versions continually changing.

We have Azure and GCP in place. Amazon provides a hybrid solution, so people are accustomed to adapting all these technologies. Cost is the only factor that is challenging.

AWS Database is supporting six or seven flavors of RDS. In the next release, I would like to extend the other database as well. There is a need for extra features that are available in open source. For example, for Postgres, we have limited features of admin availability. If it were standard, it would be very helpful for the database team as well as the migration team.

For how long have I used the solution?

I have been working with AWS Database Migration Service for six years.

What do I think about the stability of the solution?

This is a stable solution. In the past six years, we have faced two or three periods of downtime for a few minutes each time.

What do I think about the scalability of the solution?

AWS Database Migration Service is scalable. The solution was configured six years ago. When the threshold is reached, the system will automatically scale up. When the threshold is reduced, the system will reduce the resources. 

We have over 10,000 users of AWS Database Migration Service.

How are customer service and support?

We contact customer service and support, through chat or a call, with any issues we encounter.

I would rate customer service and support a four out of five overall.

How would you rate customer service and support?

Positive

How was the initial setup?

The composition of AWS Database Migration Service is simple. However, each and every code that is legacy creates dynamic code. Whatever solution worked today can not be reused in the next migration. 

What's my experience with pricing, setup cost, and licensing?

On a scale of one to five, with five being a good price, I would rate AWS Database Migration Service a two.

Which other solutions did I evaluate?

We are part of a database team. We get requests from Azure on-premise and hybrid data migration as well. We work with different cloud providers. Azure is more cost-effective than Amazon. We selected Amazon because it started first.

What other advice do I have?

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

Which deployment model are you using for this solution?

Hybrid Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
PeerSpot user
VishalSharma2 - PeerSpot reviewer
Infrastructure Lead at a computer software company with 51-200 employees
MSP
Easy to use and set up, but challenges should be cleared in the pre-assessment process
Pros and Cons
  • "It's scalable."
  • "If they had some sort of functionality where, at a specific point in time, if I want to start a new job, it should automatically pick up from where it has been left rather than having people worry about the exact job number and the timing."

What is our primary use case?

We've used the product for database migration from on-prem to AWS for an Oracle database.

What is most valuable?

The ease of use is great.

It is easy to set up initially.

It's scalable.

The solution has been quite stable. 

What needs improvement?

We had challenges working with the database as it was a different kind of exit. It has blobs and other types of storage which caused issues.

If they had some sort of functionality where, at a specific point in time, if I want to start a new job, it should automatically pick up from where it has been left rather than having people worry about the exact job number and the timing. If something could be automated, that will be really helpful.

For how long have I used the solution?

I've used the solution for a while. I've used it at least over the past year.

What do I think about the stability of the solution?

It's a stable solution. That said, every technology or solution in the industry has its own challenges. It's a good solution overall as I've used it for multiple databases. In my past experience, it has worked, and it has done wonders.

What do I think about the scalability of the solution?

It is scalable. For the instances it supports, it is scalable on runtime. It'll just require downtime and can be scaled up or down accordingly.

While we don't have any active projects right now, typically, we have six or seven people on the product.

How are customer service and support?

I've had to reach out to support as there were challenges with the database data types. We had to reach out to technical support multiple times to get that sorted. In general, we've found them to be helpful and responsive. 

How would you rate customer service and support?

Positive

How was the initial setup?

The initial setup is very simple and straightforward. It's not complex. 

For us, since we have many factors involved, we took at least two to three days to configure and validate things and then run the assessment and then get to the job. The configuration does not take much. The reason we had a longer time was due to the fact that it was a huge schema, around 800 GB. Therefore, it took that much time for us to evaluate and go through a preassessment. After configuring, there were challenges we had to fix. Then, after fixing them, we came back to the migration. It's a whole process. That said, the configuration altogether itself was not as much time. It was smooth.

What's my experience with pricing, setup cost, and licensing?

While it is a paid service, I don't have many details about licensing or costs. It's not an aspect of the product I manage. That said, I would say it is worth the investment. 

What other advice do I have?

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.

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
PeerSpot user
JoshuaEfienokwu - PeerSpot reviewer
Cloud Engineer at a tech services company with 10,001+ employees
Real User
Simple migrations, easy instance creation, and secure
Pros and Cons
  • "The most valuable features of the AWS Database Migration Service are the ease of migration, beneficial storage system, security, and simple instance creation. Additionally, the cloud that is provided is more complete than other solutions."
  • "AWS Database Migration Service can become complex when testing. Other solutions, such as Microsoft Azure makes it easy to do. There are more steps to complete tasks in AWS Database Migration Service than in Microsoft Azure."

What is our primary use case?

I am using AWS Database Migration Service for migrations and relationship migrations.

What is most valuable?

The most valuable features of the AWS Database Migration Service are the ease of migration, beneficial storage system, security, and simple instance creation. Additionally, the cloud that is provided is more complete than other solutions.

What needs improvement?

AWS Database Migration Service can become complex when testing. Other solutions, such as Microsoft Azure makes it easy to do. There are more steps to complete tasks in AWS Database Migration Service than in Microsoft Azure.

For how long have I used the solution?

I have been using AWS Database Migration Service for approximately five years.

What do I think about the stability of the solution?

The stability of the AWS Database Migration Service is good.

What do I think about the scalability of the solution?

AWS Database Migration Service is scalable.

How are customer service and support?

I have not contacted support.

Which solution did I use previously and why did I switch?

I have used Microsoft Azure previously and it is overall easier to use than AWS Database Migration Service. 

What other advice do I have?

My advice to those new to this solution is for them to take notes and know all the documentation needed for the migrations.

I rate AWS Database Migration Service a nine out of ten.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
PeerSpot user
Buyer's Guide
Download our free AWS Database Migration Service Report and get advice and tips from experienced pros sharing their opinions.
Updated: March 2025
Product Categories
Cloud Data Integration
Buyer's Guide
Download our free AWS Database Migration Service Report and get advice and tips from experienced pros sharing their opinions.