The product should support new databases. RocketDB is written in C++. It is useful when we work with Kafka. The product should support more databases and not just the standard four to five databases. It will help the users to explore new avenues and not be confined to the standard ones.

The tool provides automatic backup, but the recovery is slow if something goes wrong. We need to wait for some time. If a failure happens, recovery takes some time. Meanwhile, we lose business. It would be great if it happens much faster. The cross-region replication settings are very complex. We need to do careful planning.

Amazon RDS needs to have an overall dashboard where I can view all the tables in the form of pie charts and Gantt charts. The deployment is complex, and we would like to see automated scripts. It needs to incorporate performance insights. 

To save costs, I need to shut down my server. However, Amazon has a policy of automatically restarting the server every seven days. This means that I have to repeatedly shut down the server to avoid incurring extra expenses.

The solution's version upgrade and performance could be improved.

In the next release, it would be great to see RDS provide connection pooling out of the box.

One notable improvement that could enhance the database management experience, particularly during migration scenarios, is the accessibility of the root user. Currently, challenges arise when attempting continuous migration or transferring data between cloud platforms like AWS RDS and GCP Cloud. Another potential improvement suggestion is reconsidering the policy of locking down root user access entirely. Instead, it could be beneficial to allow access to higher-level administrators or designated personnel within a company. This approach ensures that not everyone has access to the root user. Still, at least those with administrative roles can perform essential tasks such as making changes or taking a database dump for on-premise storage.

The solution needs RDS Mysql support for both MySQL 8 and MariaDB. 

The Performance Monitor they have is a little clanky, at least in regards to the UI. 

I wish they had designed a better MySQL Monitoring solution. I personally like SolarWinds DPA.

The performance is not always as good as MySQL running on its own EC2 instance. I have done some benchmarks before between EC2 instances and RDS and EC2 were better.

Being unable to select Out-file is annoying. They do support select Out-files into S3 but only on Aurora. It would be nice if they had implemented that feature in RDS MySQL.

I have seen some limitations in Amazon RDS when I try to use SSIS in an RDS world. I need an Active Directory enabled from a security perspective, which was a little painful and cost me extra. There are some advanced monitoring queries that we cannot execute because Amazon doesn't give admin privileges to the end users. We can create another supervisor, but we don't have real admin privileges.

There are some limitations regarding some of the queries and the tools. We tried data replication, and a few features available in an enterprise SQL Server are disabled in the RDS world. We need to upgrade it to an enterprise version. Amazon RDS should improve its metrics a little more.

The solution's connectivity and response logs could be improved.

I would like to see improvements in the tool's automatic restart. 

The product must add more older versions of the database engines.

There are a few aspects of database management that have room for improvement. There are a few parameters in the solution that are a bit unclear at our end as it's not understandable. So, for queries, they show them as other stuff which is not clearly mentioned. For the legends which they are giving, there should be some other help that could help us with the legends on the graphs.

The running cost could be improved.

In our company, we have not considered what needs improvement in the solution.

The solution should consider offering some email support to its users. The support team of Amazon RDS provides us with some links to go through whenever we face some issues, but it doesn't work for us.

Concerning performance, when a cluster upgrades from lower to upper config, the connection drops. This could be solved by better coding and settings and included in the next release.

It's supposed to be scalable, but we don't feel that. True, there won't be any drops. The solution they gave was to maintain our cluster at a level sufficient for our peak load. However, that will probably defeat the whole purpose of on-demand scalability. So that is certainly where we might need to rethink the solution. It actually works in real-time, but it's not at a level where we can think of five seconds or 10 seconds there. 

The product's high price is an area of concern where improvements are required.

If we do not keep track of our costs, we might face some problems.

I like using Amazon RDS because it offers quick operations for me. However, there are times when understanding how to use some of the services can be challenging, even with documentation. If I could add a feature, I'd improve navigation for related services. 

Amazon RDS should have a more user-friendly graphical user interface and include better database management options.

They should add a feature for manual SQL patching in RDS. Also, the auto-patching features have their limitations. We can't set a particular day or date of the month for auto-maintenance.

Sometimes the interface has many moving parts, which is a concern. For example, the cloud is a virtual network instead of having a dedicated VPC that handles databases, and they have it connected to the VPC that handles the main Amazon infrastructure.

If I had one that was indicated, it would make things easier because there are specific things I need when connecting to ensure accessibility. There is no need for multiple settings, considering a database cannot survive independently. Amazon RDS needs a connection to be a client, so they should tune it a bit more. In addition, uploading and having it done within a short period is challenging.

In terms of what needs to be improved, I am unable to provide appropriate feedback because we are still familiarizing ourselves with the solution. 

Some of the documents that I have seen also state that Amazon previously supported MS SQL, which is great, but we are going into the database areas of PostgreSQL and MySQL. 

With my limited experience, I have noticed that documentation management could be improved. It could be better.

A lot of the features are disabled by default. The solution should enable more features. I understand this could cause challenges to management for many clients using RDS, however.

For me, I think that it will be great to have the option to have more SQL or have a deployment allowing for configuring it with a Microsoft SQL server.

Currently, speaking of Microsoft SQL on RDS, you don't have a full option to be able to use it directly on RDS. So, it needs improvement. It will be good to have more solutions with a simple deployment. So being in one region, you should have the option to deploy the solution in another region.

The solution could improve the administration tools.

The solution could improve by adding a sandbox environment and more security.

I do not have complaints about RDS.

The solution tends to have a lot of updates. It's a very short time before we need to update again.

Technical support could be better.

They should make it cheaper for the users. 

An RDS account cannot be shared when you close it. You need an encryption key to clone the data, but you cannot share it. 

The security features could be improved.

The shortcomings stem from not Amazon RDS as a product but are related to its monitoring capabilities. I feel Amazon RDS should have a lot of functionalities to make monitoring within the database easier. Amazon RDS should provide more granularity of log entries.

Amazon RDS could improve by having more sophisticated. I use other solutions that have better technology for more difficult tasks.

Expecting to have AWS RDS custom.

If you are a very tech-savvy guy who is a DBA, there are certain limitations due to how it's been implemented. You cannot do a lot of platform-level changes if that's how it's been set up, however, it's not required actually. Those limitations have not stopped anything, not stopped us from doing anything. That said, someone more technical may not like the limitations. Platform-level changes are not allowed. 

The solution is a bit expensive. 

The only thing that needs improvement would be the pricing of the solution. Otherwise, it works very well as it is.

We don't have control over tweaking the database parameters, so we switched to Aurora.

In the next release, it would be great to have access to core parameters to improve or tweak the performance.

The Amazon RDS engine could provide features for additional databases, such as Db2. It could also provide support for other databases, such as NoSQL databases, DynamoDB, and Apache Cassandra. They could all stay under one hood.

Another improvement that Amazon could do is to market their product so that more customers can use it. With Microsoft having its own cloud Azure hosting SQL Server databases and Oracle coming up with its own cloud, there appears to be more competition. As more customers move to Amazon cloud, it will increase the utilization of the RDS, then more customers will be able to harness the power of Amazon Relational Database Service (RDS).

The fact that it is fully managed has some disadvantages, as well. I have worked on SQL Server, Oracle, and other RDBMS systems for more than 20 years. In many of these cases, I have been an administrator and required administrative privileges to perform many of the tasks that I did. As I now work on a fully managed and maintained database, it is taking me longer to figure out how to perform these same operations that I was used to doing on-premises. Essentially, having a great deal of experience as an RDBMS administrator has made it harder for me to move forward when working on a database that is fully managed. It would be helpful if they made it easier to migrate from an existing on-premises solution to the cloud-based service.

Technical support could use some improvement.

The only thing that I can say is, you have to be really careful about the Cloud provision plannings - meaning that you should calculate the cost carefully due to the fact that the bill is increased sharply if you increase the limit. You have to provision what you need per month.

The solution charges for technical support, which is something they should change, at least for those organizations on tier one.

RDS doesn't have shell access. This could be beneficial, especially for Oracle databases.

One benefit of having shell access with RDS is that DBAs or developers could keep their own existing scripts. Especially in the case of non-enterprise versions, there is always a need to dig into performance issues and their troubleshooting. So shell access could be very handy in that case and in some other cases.

It would be better if it integrated seamlessly with Microsoft products. Our clients use the Microsoft Tally application server. We already tried to create a reputation, for example, an on-premises environment from our client to Amazon RDS using the Microsoft Tally server. But we couldn't do that because we didn't have a strong user in RDS. We couldn't create a reputation from an on-premises environment from the Microsoft Tally server to RDS. I think that it would be a good implementation, and it would help us with this case.

The price could be better. We have better options like Microsoft Azure to use in the cloud. I also don't think it's very scalable. 

Migration to RDS using the default tools is very complicated.

When you are using it for the first time, it is a little bit hard to configure. The first-time configuration is not very easy. It should be easier to configure.

Its installation should also be simpler. Currently, its installation is very complex.

With SQL Server, we have access to the SQL Server analysis services and reporting services, but such services are not available with Amazon RDS.