Amazon Relational Database Service (Amazon RDS) is a database-as-a-service (DBaaS) from Amazon Web Services.
N/A
Oracle Database
Score 8.3 out of 10
N/A
Oracle Database, currently in edition 23ai, is a converged, multimodel database management system. It is designed to simplify development for AI, microservices, graph, document, spatial, and relational applications.
$0.05
per hour
Azure SQL Database
Score 8.4 out of 10
N/A
Azure SQL Database is Microsoft's relational database as a service (DBaaS).
Oracle Database can be more expensive in comparison to Amazon RDS. This may be because of licensing fees. Installation can be a bit messy and take longer than necessary. The user interface could also use some work when compared to Amazon RDS. Some companies will need a DBA to …
Oracle Autonomous Database is designed for Oracle Database workloads, making it suitable for organizations with existing Oracle investments. RDS supports various database engines. Autonomy and Automation: Oracle Autonomous Database places a strong emphasis on automation for …
Installing, configuring, and managing Oracle Database can be challenging, especially for people who are new to Oracle products. Longer learning curves and higher operational overhead can be caused by this complexity. Amazon Relational Database Service is easy to understand and …
In a few words, we are just to confortable working with oracle and sql server. Using RDS add another layer of distributed database in order to backup everything we have in case of a disaster and also complies with authorities locally and internacionally. All database we use, …
Amazon Relational Database Service (RDS) offers sql server version compatibility for earlier versions, but azure provides only for the latest version. Amazon Relational Database Service (RDS) offers higher storage for each database instance. I think Amazon Relational Database …
Earlier we were using the Azure Ecosystem but we faced some issues in DevOps side so we decided to migrate towards some other reliable infra so we migrated all our engines, RDS and other services to Amazon Relational Database Service (RDS) and from that time we are using this. …
Every traditional rational Database requires server installation & accessing needs to be monitored periodically manually. But Amazon provides easy-to-access and monitor health and scale-up and scale-down option just by clicks without adding any additional hardware.
Amazon Relational Database Service (RDS) is an excellent option for those using AWS already, and provides a scalable, performant, database engine. Unlike Azure SQL Server it has a limit on the number of databases you can hold. However, if you're already in the AWS ecosystem it …
Amazon RDS is more resilient and accepted industry wide when compared to its peers. Also, as we have other services on AWS so it would be easier to integrate with other services like ECS if we go with Amazon RDS. Furthermore, it would be more cost effective if we go with Amazon …
We needed to use PostgreSQL due to it being the database engine that our application vendor uses. Once we were constrained on the database engine choice then Microsoft products (eg. SQL Server), whether on premise or in the cloud, were not appropriate. Therefore the only …
we could use Azure SQL for our project but as our other parts of the solutions existed on AWS, it was a better choice to have AWS RDS or else traffic exiting AWS would have taken a lot of cloud changes. Microsoft SQL Server requires license, either core-based or full license …
In my opinion, Amazon Relational Database Service (RDS) has provided better services in terms of Scalability and data Security as compared to its competitor. It helped us to manage our data using RDS server more efficiently and effectively. The high Availability helped us to …
Cloud Engineer - IT Emerging Talent Rotational Program
Chose Amazon Relational Database Service (RDS)
Whether using AWS, GCP, or Azure, you get the most value out of using applications from the same suite. Since my organization is AWS first, I am using RDS because it provides the most value for us using it with the other AWS offerings
amazon provides wide range of support for multiple database engines so we dont have to look for any other providers integration with aws ecosystem so we can seemlessly use other aws services connected to database aws have data points globally so it if data needs to be in …
We try to use Azure Databases, but we encountered issues of combining services between AWS and Azure, so this is the main reason we decided to move with Amazon RDS. I can say that between services they're quite alike but it all depends what cloud provider you use for the other …
As a POC, we had worked with Azure and GCP's databases as well. One problem with Azure is that it seems slow in supporting new versions of MySQL. With GCP Cloud SQL, the security configuration for the database was not as intuitive as in AWS. The UI in both Azure and GCP was …
I selected AWS RDS over Azure because of the [number] of products AWS has that work together. The cost for RDS was cheaper than Azure's SQL also. I use Azure for MSSQL workloads and AWS for MySQL workloads. Probably the main reason was we wanted to use S3 and Azure doesn't have …
Amazon Relational Database Service (RDS) is very well integrated with AWS services like CloudWatch, Lambda, IAM, Secrets Manager, S3, etc. It is AWS managed database service. It provides a serverless version using Aurora with auto-scaling features. Its features like …
Oracle Database 12c is able to handle large quantities of data with extremely good performance. My organization happens to be the largest user of the ERP software that we run, and it is able to handle tables with millions of rows.
Amazon Relational Database Service is the other obvious competitor. We were already in Azure, so it's not a serious contender for our business due to that bias already, but I do personally find the marketing and documentation of RDS more intimidating to sort through.
Oracle Database is "the" serious database. There really is no competition in that field. SQL Database would be a serious competitor through the ease of implementation and the "no maintenance," but since it's too expensive for "normal" use (medium to small applications), it just …
I selected Azure SQL because it integrates nicely with the technology stacks we currently maintain. The pricing is right, and clients are happy with that. Scaling is easy. Most of our clients don't want to maintain a full-blown database server, and they don't need one. For …
Azure SQL Database can be setup in minutes, not days like with Oracle
Verified User
Employee
Chose Azure SQL Database
Amazon's RDS offering is actually very good and is used in other parts of the company, we just have a lot of Azure experience so wanted to leverage that.
The simplicity and great features and good support of Microsoft as well as the more reasonable flexible price than other competitors is one of the important reasons for choosing it.
It is very easy to setup SQL database on Azure. one can always refer to their documentation for best practices. It is highly available and scalable. It is cheaper than its alternatives and provide better performance than others. As we are using many other services of Azure for …
As we were early adopters with Azure and landed on the Azure PaaS (Platform as a Service), it made sense to use databases that were on the same platform as the application to save on costs. Also, we were impressed with the simplicity of Azure SQL. From a management perspective …
If your application needs a relational data store and uses other AWS services, AWS RDS is a no-brainer. It offers all the traditional database features, makes it a snap to set up, creates cross-region replication, has advanced security, built-in monitoring, and much more at a very good price. You can also set up streaming to a data lake using various other AWS services on your RDS.
We migrated from NoSQL to an Oracle database. One of the reasons was robust backup and recovery options available in the Oracle database, which provide zero data loss. A transactional database like Oracle is a better fit for our use case than NoSQL. On a large scale, deployment was evaluated as a cheaper option than the NoSQL engine. This conclusion came even after considering Oracle license is expensive.
We have found it's a great alternative for making older legacy applications work with online databases instead of only on-premises databases. We've converted over a dozen applications this way, and it has allowed our clients to have a distributed workforce using their applications without incurring the expense of a complete application rewrite.
Automated Database Management: We use it for streamlining routine tasks like software patching and database backups.
Scalability on Demand: we use it to handle traffic spikes, scaling both vertically and horizontally.
Database Engine Compatibility: It works amazingly with multiple database engines used by different departments within our organization including MySQL, PostgreSQL, SQL Server, and Oracle.
Monitoring: It covers our extensive monitoring and logging, and also has great compatibility with Amazon CloudWatch
Maintenance is always an issue, so using a cloud solution saves a lot of trouble.
On premise solutions always suffer from fragmented implementations here and there, where several "dba's" keep track of security and maintenance. With a cloud database it's much easier to keep a central overview.
Security options in SQL database are next level... data masking, hiding sensitive data where always neglected on premise, whereas you'll get this automatically in the cloud.
It is a little difficult to configure and connect to an RDS instance. The integration with ECS can be made more seamless.
Exploring features within RDS is not very easy and intuitive. Either a human friendly documentation should be added or the User Interface be made intuitive so that people can explore and find features on their own.
There should be tools to analyze cost and minimize it according to the usage.
One needs to be aware that some T-SQL features are simply not available.
The programmatic access to server, trace flags, hardware from within Azure SQL Database is taken away (for a good reason).
No SQL Agent so your jobs need to be orchestrated differently.
The maximum concurrent logins maybe an unexpected problem.
Sudden disconnects.
The developers and admin must study the capacity and tier usage limits https://docs.microsoft.com/en-us/azure/azure-subscription-service-limits otherwise some errors or even transaction aborts never seen before can occur.
Only one Latin Collation choice.
There is no way to debug T-SQL ( a big drawback in my point of view).
We do renew our use of Amazon Relational Database Service. We don't have any problems faced with RDS in place. RDS has taken away lot of overhead of hosting database, managing the database and keeping a team just to manage database. Even the backup, security and recovery another overhead that has been taken away by RDS. So, we will keep on using RDS.
There is a lot of sunk cost in a product like Oracle 12c. It is doing a great job, it would not provide us much benefit to switch to another product even if it did the same thing due to the work involved in making such a switch. It would not be cost effective.
I've been using AWS Relational Database Services in several projects in different environments and from the AWS products, maybe this one together to EC2 are my favourite. They deliver what they promise. Reliable, fast, easy and with a fair price (in comparison to commercial products which have obscure license agreements).
Many of the powerful options can be auto-configured but there are still many things to take into account at the moment of installing and configuring an Oracle Database, compared with SQL Server or other databases. At the same time, that extra complexity allows for detailed configuration and guarantees performance, scalability, availability and security.
The interfaces are intuitive once you are familiar with all the functions. The ability to use different tools to interact with the platform, such as directly via a browser or code editors such as VS Code or Visual Studio is a great option and allows for integrating withn the project and other testing and developing tools.
I have only had good experiences in working with AWS support. I will admit that my experience comes from the benefit of having a premium tier of support but even working with free-tier accounts I have not had problems getting help with AWS products when needed. And most often, the docs do a pretty good job of explaining how to operate a service so a quick spin through the docs has been useful in solving problems.
1. I have very good experience with Oracle Database support team. Oracle support team has pool of talented Oracle Analyst resources in different regions. To name a few regions - EMEA, Asia, USA(EST, MST, PST), Australia. Their support staffs are very supportive, well trained, and customer focused. Whenever I open Oracle Sev1 SR(service request), I always get prompt update on my case timely. 2. Oracle has zoom call and chat session option linked to Oracle SR. Whenever you are in Oracle portal - you can chat with the Oracle Analyst who is working on your case. You can request for Oracle zoom call thru which you can share the your problem server screen in no time. This is very nice as it saves lot of time and energy in case you have to follow up with oracle support for your case. 3.Oracle has excellent knowledge base in which all the customer databases critical problems and their solutions are well documented. It is very easy to follow without consulting to support team at first.
We give the support a high rating simply because every time we've had issues or questions, representatives were in contact with us quickly. Without fail, our issues/questions were handled in a timely matter. That kind of response is integral when client data integrity and availability is in question. There is also a wealth of documentation for resolving issues on your own.
Overall the implementation went very well and after that everything came out as expected - in terms of performance and scalability. People should always install and upgrade a stable version for production with the latest patch set updates, test properly as much as possible, and should have a backup plan if anything unexpected happens
Amazon Relational Database Service (RDS) stands out among similar products due to its seamless integration with other AWS services, automated backups, and multi-AZ deployments for high availability. Its support for various database engines, such as MySQL, PostgreSQL, and Oracle, provides flexibility. Additionally, RDS offers managed security features, including encryption and IAM integration, enhancing data protection. The pay-as-you-go pricing model makes it cost-effective. Overall, Amazon RDS excels in ease of use, scalability, and a comprehensive feature set, making it a top choice for organizations seeking a reliable and scalable managed relational database service in the cloud.
Because of a rich user base and support for any critical issue, this is one of the best options to choose. In case the project has a TCO issue, it can compromise and choose Postgres as the best alternative. SQL server is also good and easy to code and maintain but performance is not as good as the Oracle
We moved away from Oracle and NoSQL because we had been so reliant on them for the last 25 years, the pricing was too much and we were looking for a way to cut the cord. Snowflake is just too up in the air, feels like it is soon to be just another line item to add to your Azure subscription. Azure was just priced right, easy to migrate to and plenty of resources to hire to support/maintain it. Very easy to learn, too.