AWS Database Migration Service Reviews

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

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.

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.

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

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.

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.

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.

Positive

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. 

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

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.

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

I use AWS Database Migration Service to migrate Oracle databases and PostgreSQL databases. I work with both databases and work with different migration scenarios.

The tools are very user-friendly. You can have instances or replications instances from the databases with two or more clicks. The console is also very user-friendly, and it's very easy to create new instances for migration purposes. 

I think that Amazon needs to improve the migration scenarios after analytics. We need more migration tools or more specific tools for migration and licenses. It's a very complicated scenario because, in some cases, we need specific licenses to create new instances, and some instances are very expensive. That's a very manual scenario.

I have been using AWS Database Migration Service for about one and a half years.

AWS Database Migration Service is a stable solution. It's good for me.

I'm very impressed with its scalability.

AWS has very good support for this, and that's why my customers choose AWS for deploying their resources in the cloud.

In the beginning, the initial setup was very hard, but then it became very easy. The information that the customer gives us isn't complete, and this is the most complex part of the process. Then we use some tools because we need to consider the indexes, tables, and other things in our databases.

Pricing can be improved. In some cases, the price of the instances are very expensive.

Our clients evaluated other options like Google Cloud, Oracle Cloud, and Huawei Cloud. I think AWS Database Migration Services is a very robust solution compared to other cloud providers.

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.

We are using the solution for a database migration.

I like that I can focus on the logic and I don't have to worry about the administration stuff. AWS handles that for me.

There's some functionality that we're waiting on, like the problem scheduler. It's not yet supported in the current product.

The solution could use schedule linking. I'm keen to get that from the solution in the future.

We haven't had any issues with the stability of the solution. It's quite stable.

The solution rates high on scalability. It's very good. We're still migrating, but right now, we have about 100-150 users per day.

Support could be more expedient. Right now I am waiting on support for an extension.

We didn't previously use another solution.

The initial setup had a medium amount of difficulty. It's not overly complex. It's not also straightforward. We're trying to put everything in post. There's a bit more complexity in the implementation process. We're still in the middle of migration, so I'm not sure how long deployment will actually take to complete.

We evaluated HVR as well as DMS. We ultimately chose DMS because of the costs and the licensing they offered. Also, our needs were quite simple. We didn't really need HVR to do the migration.

We are using the public cloud deployment model.

I would rate the solution eight out of ten.

We don't use Data Migration Services regularly. We only use it when we need to migrate a relatively large database from on-premises to the cloud. From my point of view, it was the best option in this case.

It provided the ability to create more, less optimized data warehouses. And simplify support and working with data.

It's pretty useful when we need to migrate something big from a different type of database that AWS Data Migration Services supports. But it's more convenient to use Glue if we're dealing with a regular data load, like migrating a table.

Database Migration Service could be more integrated. I think that it makes sense to add integration to these functions. For example, AWS Glue has a feature called Orchestrator to create data flows, and that's more straightforward. But it's not easy to do the same things with Database Migration Service.

Database Migration Service is stable.

I would say Database Migration Service is not expensive. 

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. 

We use this program to migrate from SQL to RDS, or from Oracle to RDS, or from Oracle to Aurora and so on.

I find the DNS services to be the most valuable feature.

The pricing can be better and it should be more competitive, so I would like to see an improvement there.

I have been using AWS Database Migration Service for more than ten years now.

The program is very stable.

I was very impressed by the scalability of AWS Database Migration Service. One of our clients has more than 15,000 users.

We don't really use their technical support but I believe the technical team will be able to help with any issues that may arise.

The initial setup was really easy and it took us about an hour to set everything up. We have our own team of about 45 people that was responsible for the implementation. The maintenance of the program is mostly automatic.

It is a very expensive program and you pay a license fee based on the amount of users you have. And besides the license fees, there are additional costs for migration.

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. 

We're primarily using the solution to migrate our archive and data, which we are storing in our local servers, to the cloud.

The solution's most valuable feature is its warning of the costs of the migration.

As the solution is on the cloud, we don't have to worry about the maintenance of software.

The administrative aspects of the solution are very good. When we need to, we can increase our speed.

It would be helpful if the bandwidth could be independent of the network or if we could have a dedicated bandwidth for this product.

In terms of dedicated bandwidth, if it can be support Excel or prioritize Excel based on the data it is going to transfer, it would be better.

I've been using the solution for six months.

The solution is quite stable.

The solution is quite scalable. We have more than 100 users currently on the solution.

I've never reached out to technical support.

The initial setup was straightforward. It's easy to deploy and takes about 40 to 45 minutes. It does depend on the server and configuration, however. 

I'm a consultant. We use the public cloud deployment model.

I'd rate the solution seven out of ten.