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
MySQL
Score 8.3 out of 10
N/A
MySQL is a popular open-source relational and embedded database, now owned by Oracle.
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
Pricing
Microsoft Access
MySQL
Oracle Database
Editions & Modules
Microsoft Access
$139.99
per PC
No answers on this topic
Oracle Base Database Service - Standard
$0.0538
per hour
Oracle Base Database Service - Enterprise
$0.1075
per hour
Oracle Base Database Service - High Performance
$0.2218
per hour
Standard Edition
Contact Sales
Enterprise Edition
Contact Sales
Personal Edition
Contact Sales
Offerings
Pricing Offerings
Microsoft Access
MySQL
Oracle Database
Free Trial
No
No
Yes
Free/Freemium Version
No
No
Yes
Premium Consulting/Integration Services
No
No
No
Entry-level Setup Fee
No setup fee
No setup fee
No setup fee
Additional Details
—
—
—
More Pricing Information
Community Pulse
Microsoft Access
MySQL
Oracle Database
Considered Multiple Products
Microsoft Access
Verified User
Analyst
Chose Microsoft Access
Microsoft Access is better for novice users. It is very user-friendly and helps beginners learn data base rather than MySQL. MySQL is for more advanced users which have more experience. Access is also good for smaller organizations. It saves money rather than spending more on …
Microsoft Access databases are more suitable for us because we are a smaller team. It's easy for us to export the reporting. It's also easy for people to create their own databases as well! Microsoft Access is honestly a one-stop-shop for us, and we figured we were not at a …
Tableau is not even a 'switch-out' tool, it's for visualization so it's not a fair comparison. Against other databasing tools, MySQL is still my favorite may be simply due to being a creature of comfort because that's where I first learned to manage DB. However, Microsoft …
[Selected Microsoft Access for] employee learning simplicity, attractive graphical environment and features of Microsoft 365 with responsive Microsoft support.
Being a similar "Windows application" it's easier to start to use as part of Office. Also, the GUI capabilities are much more advanced than other high-performance databases.
Verified User
Consultant
Chose Microsoft Access
Microsoft Access is a bit dated compared to other database tools. It is slower, not able to handle quantities of data that are as large as the other tools, and a bit more finicky. However, it is sometimes the preferred tool for some clients. It also has a lower barrier to entry …
Verified User
Employee
Chose Microsoft Access
MS Access is the little brother to all these products. In no way is it as feature-rich as the competition I have selected. It is, however, great when used properly. It does not have the same level of security, availability, access, or recoverability as anything listed above. …
Access should be relatively cost effective because it is included in the MS office 365. But it is not suitable for larger organization due to lack of work sharing environment.
We selected Microsoft Access for its lower price and because it is easy to use for any user. Previously in the company, because we were small, Excel was used and I can migrate my data from Excel to Access in a fast and simple way. Besides that, it has organized information that …
Verified User
Analyst
Chose Microsoft Access
Microsoft Access is a good data management tool. and it excels in that area, which is what we needed the most. It was simple to use and easy to learn. Database management can be done with multiple users in Access. And we can have reports for data summaries, or for any specific …
I find access easier to use than base or thunderbird but if you are familiar with Microsoft Office products, the learning curve is lessened by that. There is no comparision to SQL or MySql, but these are meant for larger more robust database applications. Access was actually in …
Microsoft Access can be used on the Windows platform, which most organizations use, especially our own, which is one of the reasons why we selected Microsoft Access. Access was also part of the standard Windows image that our company uses when imaging desktops and laptops so …
MySQL
Verified User
Manager
Chose MySQL
We use Oracle Database for another business unit and in the recent past I’ve used Microsoft Access. While every relational database has its positives and negatives, MySQL has proven to be the fastest and most reliable. Its automated backups have saved us time in redoing mass …
It would be hard to make a case for the use of Microsoft Access for any but the most simple of internal business applications at this stage, not because it is a bad product but it falls well short of the power and scalability of MySQL and almost any other databse solution out …
MySQL offers some of the features as Oracle Database 12c, however, there are many crucial ones that are missed. Features such as OLAP, really make Oracle Database 12c a clear winner here. We use both databases in our organization for separate reasons, MySQL for prototyping, and …
Of course compare to no SQL databases it's slower but there is a completely different use case for them... In my opinion it is better than PostgreSQL, it's easier to configure and has the same performance, or approximately the same. Of course Oracle Database is a way bigger …
MySQL was the first option due to the existing knowledge, and after using other databases, it also appeared to be the most predictable in terms of costs
Rest all the big brand databases incure high licensing cost giving almost the same value that MySQL is giving being an open source database. Other databases like Oracle, MS SQL servers need extensive resource along with a huge team to manage those databases. However, thats not …
Our original implementation of MySQL was to replace an Access database that had unfortunately been able to grow beyond its abilities and scope. MySQL seemed to offer all the benefits of Access (easy to set up, use and administer) with none of the downsides (reliability, …
As I have been commenting in our company, we have solved our performance problems and responses obtaining speed in the queries occupies less disk space, in addition to its price and all the tools of great Scope it possesses.
Having used both PostgreSQL and Microsoft SQL Server, I can tell that MySQL performs admirably in a Linux setting. When compared to Microsoft SQL Server, the extra benefit is the minimal or nonexistent licence fee. We find that MySQL's programming interface is particularly …
Before MySQL, our team was exploring and evaluating different options for a good RDMS (relational database management system) service. We explored Oracle, MSSQL, and Google BigQuery. Most of these are costly and not easy to maintain in the long run in terms of price especially …
MySQL has most of the functionality of other, very costly, alternatives without the big price tag. It is open-source with improvements coming at a relatively good rate. It is not as robust as those other offerings and can have some challenging points at scale for large …
Microsoft SQL can be considered as an enterprise level software since it is recommended for large businesses. Microsoft SQL has some unique categories like big data processing, DBMS, etc. whereas MySQL is not capable of handling such features. I guess this is how these both …
MySQL has a GUI which makes it easy for developers to work upon. It has all features like replication, backup and crash recovery. Also since it is freely available it becomes commercially feasible for people to use this DB. Also MySQL can be easily used as a back end for the …
I would choose Oracle 11g, 12c for more complex ventures which require financials and complex logic. I would choose MySQL for simpler applications which simply need to interface data to a backend. I selected MySQL in this case because it is free and much simpler to install—it …
Familiarity: With MySQL, I know what to expect, and that goes a long way. Also, since it adheres fairly close to SQL '92, It's relatively easy to construct queries, views, etc. without a steep learning curve. Also, RAM usage is important (this is true of any RDBMS …
SQLLite was not a choice on Trust Radius, and it is the only tool that I have used similar to MySQL and the use was several years ago, so I do not remember the exact reason but there was some function that I needed that SQLite could not perform, and I had to download MySQL to …
We have used Oracle as our clinical databases that stores patient records. In this project we didn't used Oracle but separately built MySQL based data infrastructure as this is an independent scientific research project. Oracle is great overall, with most of functionalities …
Cuts down seperate charges for additional databases as in Microsoft SQL Server. It is an open source software compared to other database management systems.
I've used both Oracle and MySQL. I like both database technologies. Both of them provide great solutions. Each one has their own benefits based on the requirement and right environment. The point is to find the right environment to use and compare price/performance/scalability.
Compared to Oracle MySQL is lacking some of the advanced features Oracle provides but through a detailed business and technical requirements capture process it became clear we would not need these very advanced features. Oracle is stronger on the backup and restore side of …
MySQL does not provide anywhere near the user interface or features that Oracle Database 12c provides. Building REST endpoints on MySQL is a much more challenging process and integrating it with a web app is much more complicated than building an ORDS endpoint within the Oracle …
We currently use all of the above database technologies in different applications, but where the application is mission-critical we use Oracle. Microsoft SQL Server is good for canned applications such as back-office or HR. MySQL does not have the same level of logging or …
IBM DB2 is extremely heavy as compared to Oracle and is expensive for the price we pay for the product. MySQL doesn’t have most of the features that Oracle has.
Oracle is placed in a good spot against its competitors. It has advantages over its competitors in its legacy stability and high availability. A common engine to handle relational, JSON, Vector, and graph data makes it more cost-effective. Given all the good features, the …
The Oracle database was selected before I started working on the project, so I can't tell the reasons behind the choice. However, it was recognized as the best suited for holding several million records for related entities and was preferred over NoSQL options.
Oracle 12c is good for all business applications but still consider Microsoft SQLServer for internal/other applications to save on cost.
Verified User
Consultant
Chose Oracle Database
Oracle Database is best in business, consistent, and robust. Even the standard version is sufficient for the best performance. The main thing is I have never seen corruption and in my opinion, it is best when used with Linux.
Verified User
Engineer
Chose Oracle Database
Microsoft SQL is just as stable and almost as sellable with a much lower cost of ownership (staff and licensing). But as our primary application doesn't support Microsoft SQL we had to license Oracle.
Exadata is expensive and we decided to switch to 12c for the sake of consolidating and keep up with Oracles initiative to move towards cloud. Maybe in the future.
Oracle is more of an enterprise-level database than Access and SAP Adaptive Server Enterprise isn't getting developed much (some people wonder how close it is to end of life) but SQL Server is miles ahead of Oracle IMO in terms of user experience and comparable in terms of …
Oracle 12c is able to support daily operations that might be required. Of course, Exadata is a powerful machine that is definitely fit for big scale but requires high demand of both CPU, IO, and memory processing. Also the one engineered system saves lots of time to build the …
It's the Oracle Support that beats everything else, and a solid contract. Also, all the other features that support Oracle are way ahead of other products.
Oracle completed solution and support is of cause better than open source solutions, we also choose other NoSQL database and Graph database, to address some very particular business use cases
It's easy to scale an Oracle database compared to any others, it's easy to manage many Oracle databases together with lots of administrative and security features.
1. The commercial application required an Oracle database running at the back end 2. Existing Oracle expertise makes it easy to manage an Oracle database 3. Confidence in Oracle databases: No need to worry about performance, scalability.
For some implementations in my company, Oracle Database was selected because all the support, experience, features, continuing development, etc that the product and Oracle's company has been providing so far, but also, it was selected by the system's company that my …
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.
MySQL is best suited for applications on platform like high-traffic content-driven websites, small-scale web apps, data warehouses which regards light analytical workloads. However its less suited for areas like enterprise data warehouse, OLAP cubes, large-scale reporting, applications requiring flexible or semi-structured data like event logging systems, product configurations, dynamic forms.
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.
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.
Learning curve: is big. Newbies will face problems in understanding the platform initially. However, with plenty of online resources, one can easily find solutions to problems and learn on the go.
Backup and restore: MySQL is not very seamless. Although the data is never ruptured or missed, the process involved is not very much user-friendly. Maybe, a new command-line interface for only the backup-restore functionality shall be set up again to make this very important step much easier to perform and maintain.
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.
For teaching Databases and SQL, I would definitely continue to use MySQL. It provides a good, solid foundation to learn about databases. Also to learn about the SQL language and how it works with the creation, insertion, deletion, updating, and manipulation of data, tables, and databases. This SQL language is a foundation and can be used to learn many other database related concepts.
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.
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 give MySQL a 9/10 overall because I really like it but I feel like there are a lot of tech people who would hate it if I gave it a 10/10. I've never had any problems with it or reached any of its limitations but I know a few people who have so I can't give it a 10/10 based on those complaints.
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.
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.
We have never contacted MySQL enterprise support team for any issues related to MySQL. This is because we have been using primarily the MySQL Server community edition and have been using the MySQL support forums for any questions and practical guidance that we needed before and during the technical implementations. Overall, the support community has been very helpful and allowed us to make the most out of the community edition.
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.
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
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.
MongoDB has a dynamic schema for how data is stored in 'documents' whereas MySQL is more structured with tables, columns, and rows. MongoDB was built for high availability whereas MySQL can be a challenge when it comes to replication of the data and making everything redundant in the event of a DR or outage.
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