Amazon Relational Database Service (Amazon RDS) is a database-as-a-service (DBaaS) from Amazon Web Services.
N/A
Microsoft Access
Score 7.6 out of 10
N/A
Microsoft Access is a database management system from Microsoft that combines the relational Microsoft Jet Database Engine with a graphical user interface and software-development tools.
$139.99
per PC
SolarWinds SQL Sentry
Score 10.0 out of 10
N/A
SolarWinds SQL Sentry is designed to help data professionals optimize SQL Server database performance
in physical, virtual, and cloud environments. SQL Sentry delivers metrics to help users find and fix database performance problems
and provides scalability, boasting demonstrated success monitoring 800+ SQL
Server instances with one monitoring database. With
SQL Sentry, the user can monitor:
SQL Server
Azure SQL
Database
SQL Server
Analysis…
$0
Free
Pricing
Amazon Relational Database Service (RDS)
Microsoft Access
SolarWinds SQL Sentry
Editions & Modules
Amazon RDS for PostgreSQL
$0.24 ($0.48)
per hour, R5 Large (R5 Extra Large)
Amazon RDS for MariaDB
$0.25 ($0.50)
per hour, R5 Large (R5 Extra Large)
Amazon RDS for MySQL
$0.29 ($0.58)
per hour, R5 Large (R5 Extra Large)
Amazon RDS for Oracle
$0.482 ($0.964)
per hour, R5 Large (R5 Extra Large)
Amazon RDS for SQL Server
$1.02 ($1.52)
per hour, R5 Large (R5 Extra Large)
Microsoft Access
$139.99
per PC
Plan Explorer (SQL Server Query Tuning)
$0
Free
SQL Sentry for Azure SQL Database
$161
Per year per database (annual subscription)
SQL Sentry
1,450
Per year per instance (annual subscription)
Offerings
Pricing Offerings
Amazon RDS
Microsoft Access
SolarWinds SQL Sentry
Free Trial
No
No
Yes
Free/Freemium Version
No
No
No
Premium Consulting/Integration Services
No
No
Yes
Entry-level Setup Fee
Optional
No setup fee
No setup fee
Additional Details
—
—
—
More Pricing Information
Community Pulse
Amazon Relational Database Service (RDS)
Microsoft Access
SolarWinds SQL Sentry
Considered Multiple Products
Amazon RDS
Verified User
Consultant
Chose Amazon Relational Database Service (RDS)
Amazon Relational Database is more reliable and effective than the one I am using. Amazon Relational Database has more storage capacity and is easily accessible. Amazon Relational Database has multiple options. Amazon Relational Database cloud services are excellent. From the …
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.
As a Material Purchasing/Planning/inventory tracking application, Microsoft Access serves its purpose well. It's presentation is clean, data entry is simple and the ability to customize search fields is welcome. It does, however, come with some caveats; namely, when setting search filters and the need arises to back up a step or two, with Microsoft Access you have to reset, or "clear all", adding extra steps/time to a query.
This solution is perfect for a team with a large server count and, at least, moderate experience supporting a SQL Server environment. If the environment is smaller or the team has less experience working with SQL Server performance tuning methodologies, then the tool may be overwhelming for the users.
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
The Top SQL functionality has been extremely useful for identifying poorly performing queries by resource consumption.
The flexibility of creating your own Advisory Conditions has allowed us to integrate our custom internal alerts into a centralized dashboard and alerting platform.
Being able to highlight any chart on the dashboard and then tool-matching that window across all the other charts makes it much easier to correlate the different performance metrics against each other.
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.
Microsoft Access has not really changed at all for several years. It might be nice to see some upgrades and changes.
The help info is often not helpful. Need more tutorials for Microsoft Access to show how to do specific things.
Be careful naming objects such as tables, forms, etc. Names that are too long can get cut off in dialog boxes to choose a table, form, report, etc. So, I wish they would have resizable dialog boxes to allow you to see objects with long names.
I wish it could show me objects that are not in use in the database for current queries, tables, reports, forms, and macros. That way unused objects can be deleted without worrying about losing a report or query because you deleted the underlying object.
Tuning advice: With all the graphs and data available, it's not always easy to determine the best thing to do. I'd like to see SentryOne provide some best practice analysis based on the historical information collected for the server being looked at.
They could add help tips or links to help documents, when you select a graph on the dashboard. Inexperienced users tend to put blinders on and focus on one thing when they see a high counter or something out of the ordinary. It would be very useful to include a link that provides underlying help. The link would provide an explanation of the counter in detail and offer possible explanations as to why the counter is off.
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.
I and the rest of my team will renew our Microsoft Access in the future because we use and maintain many different applications and databases created using Microsoft Access so we will need to maintain them in the future. Additionally, it is a standard at our place of work so it is at $0 cost to us to use. Another reason for renewing Microsoft Access is that we just don' t have the resources needed to extend into a network of users so we need to remain a single-desktop application at this time.
Absolutely. SQL Sentry is an absolute must have for any company with a SQL Server estate. It provides a force multiplier to effectively manage SQL Server, and the feature sets are second to none. The support and expertise at SentryOne is incredible. They are very supportive of both the platform users and helping your business with the product
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).
Microsoft Access is easy to use. It is compatible with spreadsheets. It is a very good data management tool. There is scope to save a large amount of data in one place. For using this database, one does not need much training, can be shared among multiple users. This database has to sort and filtering features which seem to be very useful.
I accept that the flexibility of the alerting comes at a price. Other than the alerting SQL Sentry's interface is intuitive. Connecting to a new SQL instance, given that all the needed ports are open in your firewalls is straight forward. Reviewing the performance and queries for an instance is available in with a right click. As you dig in new tabs are created to present the detailed data. I find the ability to filter and rollup metrics on a query very helpful in dealing with the "it's running slow". You can easily compare the metrics of run times for the same query to let the user know, it's probably data your doing a billion reads instead of the usual 100 thousand.
The system is working perfectly in capturing data, but we do experience issues with SQL Timeout when viewing results in the remote clients. This may be due to the fact that our monitoring service is consuming most of the CPU, and it is the same server that is hosting the SQL Repository. We could probably fix the issue by separating the SQL instance from the monitoring service.
In most cases the pages load very quickly. In our particular case, we need to do some movement of services to separate our monitoring service to separate infrastructure from the repository. When we first started with SQL Sentry on 5 licenses, we did not have any issues. Since we have now grown that to 25, we are experiencing some challenges. We do not believe this to be a tool problem
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.
While I have never contacted Microsoft directly for product support, for some reason there's a real prejudice against MS Access among most IT support professionals. They are usually discouraging when it comes to using MS Access. Most of this is due to their lack of understanding of MS Access and how it can improve one's productivity. If Microsoft invested more resources towards enhancing and promoting the use of MS Access then maybe things would be different.
From their infancy as a smaller company to now as a global player they have always kept focus on prioritising he customer. They know their product and the technology it supports and are easily accessible for both resolving problems with the product all the way to adding value through additional training and assisting with getting return on investment through utilisation of the many features the product provides.
Was suggested that we install the process monitors on a dev or qa database server, but we found it more useful to create an IT db server and put it there (along with a few other apps that we use for monitoring).
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.
Excel is a fantastic - robust application that can do so much so easily. Its easy to train and understand. However - excel does not provide a reporting function and that is typically where we will suggest a move to [Microsoft] Access. [Microsoft] Access requires a little more knowledge of data manipulation.
SQL Sentry offers more features and is customize-able to fit our business needs. It has more centralized management and support. The company's technical support is also top notch. It is also worth mentioning that SentryOne Team Blog is an excellent source. One can find lots of valuable troubleshooting skills on the blog site - very educational and informational.
We are running 25 instances through a single monitoring service and it is able to keep up. We are finding that this many instances in our environment is about as many as can be handled. We will need to deploy additional monitoring services. Luckily, there is no additional licensing costs to deploy additional monitoring services. For us, it's just an additional Azure VM.
Better customer service as it alerts me automatically to loss of service issues so I can react and either get things fixed before it impacts the customers or to let my management know as soon as possible
It helps me find expensive SQL so our customers get better performance and we make better use of our resources