AWS Database Migration Service Reviews

AWS Database Migration Service is a very useful tool for our organization. One example of how we use it is when we need to save the data to ensure we don't lose it. To eradicate this risk, we save the database where we can extract it through commands. We can do a lot of with just simple commands that will assist in accessing the data with ease.

Also, we can select from the API where we will use the data connections to the API where the client can easily access the data. At the day's end, we set some data from our website and view the API connection to the ABL link to the client. They can access that data to the API and the database will give the function and connect.

Saving the data that is in use is easy. We don't have any complexity like with MySQL. The database connections can be a little tricky in MySQL, it is easier with AWS Database Migration and the consistent view it provides.

We can easily access AWS Database Migration Service through not only AWS, but pgAdmin.

The price is expensive for a person or student who wants to learn how to use the solution. For students, AWS provides free access for a year. I would like to see the company provide the same access to individuals who are trying to learn the solution on their own to pursue a particular career that requires the knowledge.

We have been using Database Migration Service for two years.

AWS Database Migration Service is stable. The server has limits on how many can connect to the database, but you can extend them. 

This solution is scalable. We have approximately 40 people using AWS Database Migration Service in our company. This includes developers and the support team.

We have plans to increase our usage.

AWS provides useful documentation that helps you understand how to do everything. This includes instructional videos if you are not satisfied with the documentation. The technical team is also available and quick to respond and find a solution.

Positive

The installation is easy. You just need to provide one authentication link where you have the port numbers and the name of the database. You can access Database through API or save the data into Database. You can install it using any code that you use.

The deployment does not take much time. You can connect directly to anything, and it is quick. There are connections you should know about. 

AWS Database Migration Service is the least expensive solution, but is still expensive.

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.

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