AWS Database Migration Service Reviews

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.

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.

My clients utilize the AWS Database Migration Service for several main use cases, primarily to achieve less cost and more viability. The first is the issue of their RDS being self-managed. It demands less from the DBAs who take care of the environment. It also addresses the AWS security policy. Besides the database issue, there is the matter of the security services that AWS has. The issue of the VPC, of the private subnet, in short, all these advantages that for an on-premise environment are complicated.

There are many people who want to scale their businesses and applications but have limiting factors for traditional on-premise databases. We have been doing considerable work in this sense with the creation of PoCs and credits for the environment, so that the client doesn't have a cost with labor. The main reason clients come to us to do these migrations to AWS is that it's self-managed. The privacy policies from AWS guarantee that your database will not be attacked. Additionally, Novoli, our company, can provide a PoC to migrate your database to AWS with credits for three months of free usage to evaluate the performance. Clients also choose these migrations because of Aurora, which is a database managed by AWS.

We have utilized the continuous data replication feature of the AWS Database Migration Service. We have clients using this model of replication between databases for reading and writing.

The replication feature helps us maintain business continuity for our clients. The objective of database replication, one for writing and the other for reading, is to prevent overloading the database in terms of end-user usage, ensuring it doesn't compromise performance.

The initial setup of the AWS Database Migration Service is straightforward because we create the same data structure from the source database. We simply use the same version, the same language, such as MySQL, SQL Server, Postgres, and migrate everything to AWS. Then we replicate indexes, triggers, and procedures, so it functions exactly as it does outside AWS.

This would require input from our technical team to provide a deeper analysis of potential improvements. As I am from the commercial area, we would need to involve the technical team to address specific improvement points since they are the ones directly working with the platform.

I have eight years of experience with the AWS Database Migration Service since the company started.

Regarding pricing for the AWS Database Migration Service, the most challenging aspects are databases such as Oracle and SQL Server, which require licenses. The competition with costs from the database providers, in this case OCI or Microsoft, makes these scenarios more complicated. For open source databases such as MySQL and Postgres, the migration process is more straightforward. The most significant issue is the licensing costs, which sometimes make it difficult for AWS to compete with existing Microsoft pricing structures.

This would require input from our technical team to provide a deeper analysis of potential improvements. As I am from the commercial area, we would need to involve the technical team to address specific improvement points since they are the ones directly working with the platform. My overall rating for AWS Database Migration Service is 9 out of 10.

My main use case for AWS Database Migration Service is migrating an on-premises database to AWS, and I used it to move data securely and continuously synchronize changes during the migration process, ensuring a smooth transition to the cloud. AWS Database Migration Service enabled me to migrate an on-premises database to AWS with minimal downtime, which is a great offering from AWS.

My main valuable features of AWS Database Migration Service include the ability to move data securely and continuously synchronize changes during the migration process, ensuring a smooth transition to the cloud.

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

I would give AWS Database Migration Service a rating of 10 out of 10.