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
Microsoft Azure
Score 8.4 out of 10
N/A
Microsoft Azure is a cloud computing platform and infrastructure for building, deploying, and managing applications and services through a global network of Microsoft-managed datacenters.
$29
per month
Microsoft SQL Server
Score 8.6 out of 10
N/A
Microsoft SQL Server is a relational database.
$1,418
Per License
Pricing
Microsoft Access
Microsoft Azure
Microsoft SQL Server
Editions & Modules
Microsoft Access
$139.99
per PC
Developer
$29
per month
Standard
$100
per month
Professional Direct
$1000
per month
Basic
Free
per month
Subscription
$1,418.00
Per License
Enterprise
$13,748.00
Per License
Offerings
Pricing Offerings
Microsoft Access
Microsoft Azure
Microsoft SQL Server
Free Trial
No
Yes
No
Free/Freemium Version
No
Yes
No
Premium Consulting/Integration Services
No
No
No
Entry-level Setup Fee
No setup fee
No setup fee
No setup fee
Additional Details
—
The free tier lets users have access to a variety of services free for 12 months with limited usage after making an Azure account.
[Selected Microsoft Access for] employee learning simplicity, attractive graphical environment and features of Microsoft 365 with responsive Microsoft support.
Visual FoxPro is a discontinued software, and no longer has support. Also, very few people still use it, or ever know how to use it. Excel is very popular, but [Microsoft] Access can do things like data joins much easier and faster
Although SQL is a full-blown platform for heavy database management, Microsoft Access serves the purpose perfectly for small and mid-scale enterprises. It is also perfect for people just getting started with database management. The graphical user interface is a major plus …
Unlike enterprise-level databases, MS Access doesn't require setting up a complex server environment with user security schemes. It's an excellent tool for small scale databases where purchasing and setting up a product like MS SQL Server could be an overkill. Unlike …
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. …
Microsoft is much more simple and far less powerful. However, that is often times all that is needed for the job. Essbase is better for large organizations that have multi business units that need to pull from the same datasource.
Access is more robust than Excel in terms of data-centricity and robustness. It however isn't meant to support an enterprise-level use case like SQL Server is. That sweet spot in the middle (a departmental solution that requires more than Excel can offer) is the sweet spot for …
Nowadays it is too hard to say why and how one cloud service is better than the other. IT is probably the question that combines a lot of different aspects like price, functionality, how it looks, ease of administration, size of the infrastructure. As for me, it is more …
A few years ago we were a fairly large AWS shop. At a specific point the decision was made to go to Azure and we have been very happy with the outcome. Azure works better, integrates better, has better support and is cheaper that What we had with AWS. Simply put Azure is the …
Honestly in my opinion there is no one winner in this area. Both Azure and AWS are great in their own way. Pricewise it all depends in where you're from. Options are very similar and quality of what you get as well as the customer service are both great.
Amazon has more or less all the features like Azure. With Microsoft being a technology company, for any new feature in Microsoft, the integration will be seamless.
Microsoft Access while a data tool cannot scale to number of concurrent users or the great amount of files needed to run a business. Microsoft Access can attach to sql server as a backend but the interface is still limited to less than 20 concurrent users at a time.
Verified User
Technician
Chose Microsoft SQL Server
Microsoft SQL is slower than MySQL and Access but far more feature-rich and reliable. Access is almost obsolete nowadays, so not too many people are considering it, but unless budget or an open-source ethos is a factor, Microsoft SQL is superior in every way. Many commonly used …
All of the platforms have their own benefit. I was not the decision maker in selecting Microsoft SQL Server, as it was already being utilized when I joined the company, 7 years ago. I can say that I feel more comfortable with utilizing this platform as opposed to the other ones.
The free version is very powerfull and easy to install and use for small companies. Going to Professional and Standard, gives you all the support and the flexibility needed. It is known within the Database Administrator crew, and you can get support very easily over the …
I use Crystal and Microsoft SQL Server with each other. Each has a unique role that it brings to every query. Microsoft SQL Server allows me to write and refine my base query. Crystal allows me to take that query and make it more visually appealing and easier to interpret.
Since we run a .NET shop I'm not able to speak too much on how it compares to the alternatives. I would say in our dealings with MYSQL demonstrated that Microsoft SQL Server is less complicated to get up and running initially. The user interface of MYSQL seemed to be complex …
My experience with Microsoft SQL Server and the form to connect across multiple data connector: Flat file, CSV, Access, Oracle, MySQL, excel file, XML, JSON. Also, MS SQL has a good Reporting tool and interaction with the Web Apps like an HTTP.Requesting data. MS SQL Server is …
SQL Server is a better choice for quick time to market solutions and for easier maintenance. Oracle Database setup and programming to support solutions has a harder learning curve and it requires more time and effort to hit the ground running.
Microsoft SQL Server is more secure and offers more robustness for our data. SQL Server is also great because of its integration with Microsoft Visual Studio. It's also great because developers can build reports and stuff like that from scratch. It's faster compared to PostgreSQ…
I started working with databases many years ago with Access, which allows you to create relational database and provide an old-fashioned desktop interface. I had a look at Oracle but I never had the opportunity to get to the bottom (also because of the budget that had the …
Years ago I used Oracle and Oracle Data Integrator and I hated it. It was cumbersome and archaic and I couldn't believe the product could be so popular. Given a database related task and a choice between Oracle or Microsoft SQL Server, SQL Server wins hands down in ease of use, …
I have used Microsoft Access, MySQL, and I have been a user of systems that run on Oracle database servers. All but Oracle are really intended for smaller scale projects and teams as they start to get slow or the performance will suffer once you start getting lots of data input …
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.
Azure is particularly well suited for enterprise environments with existing Microsoft investments, those that require robust compliance features, and organizations that need hybrid cloud capabilities that bridge on-premises and cloud infrastructure. In my opinion, Azure is less appropriate for cost-sensitive startups or small businesses without dedicated cloud expertise and scenarios requiring edge computing use cases with limited connectivity. Azure offers comprehensive solutions for most business needs but can feel like there is a higher learning curve than other cloud-based providers, depending on the product and use case.
Microsoft SQL is ubiquitous, while MySQL runs under the hood all over the place. Microsoft SQL is the platform taught in colleges and certification courses and is the one most likely to be used by businesses because it is backed by Microsoft. Its interface is friendly (well, as pleasant as SQL can be) and has been used by so many for so long that resources are freely available if you encounter any issues.
Microsoft Azure is highly scalable and flexible. You can quickly scale up or down additional resources and computing power.
You have no longer upfront investments for hardware. You only pay for the use of your computing power, storage space, or services.
The uptime that can be achieved and guaranteed is very important for our company. This includes the rapid maintenance for security updates that are mostly carried out by Microsoft.
The wide range of capabilities of services that are possible in Microsoft Azure. You can practically put or create anything in Microsoft Azure.
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.
The cost of resources is difficult to determine, technical documentation is frequently out of date, and documentation and mapping capabilities are lacking.
The documentation needs to be improved, and some advanced configuration options require research and experimentation.
Microsoft's licensing scheme is too complex for the average user, and Azure SQL syntax is too different from traditional SQL.
Microsoft SQL Server Enterprise edition has a high cost but is the only edition which supports SQL Always On Availability Groups. It would be nice to include this feature in the Standard version.
Licensing of Microsoft SQL Server is a quite complex matter, it would be good to simplify licensing in the future. For example, per core vs per user CAL licensing, as well as complex licensing scenarios in the Cloud and on Edge locations.
It would be good to include native tools for converting Oracle, DB2, Postgresql and MySQL/MariaDB databases (schema and data) for import into Microsoft SQL Server.
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.
Moving to Azure was and still is an organizational strategy and not simply changing vendors. Our product roadmap revolved around Azure as we are in the business of humanitarian relief and Azure and Microsoft play an important part in quickly and efficiently serving all of the world. Migration and investment in Azure should be considered as an overall strategy of an organization and communicated companywide.
We understand that the Microsoft SQL Server will continue to advance, offering the same robust and reliable platform while adding new features that enable us, as a software center, to create a superior product. That provides excellent performance while reducing the hardware requirements and the total cost of ownership of our solution.
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.
As Microsoft Azure is [doing a] really good with PaaS. The need of a market is to have [a] combo of PaaS and IaaS. While AWS is making [an] exceptionally well blend of both of them, Azure needs to work more on DevOps and Automation stuff. Apart from that, I would recommend Azure as a great platform for cloud services as scale.
SQL Server mostly 'just works' or generates error messages to help you sort out the trouble. You can usually count on the product to get the job done and keep an eye on your potential mistakes. Interaction with other Microsoft products makes operating as a Windows user pretty straight forward. Digging through the multitude of dialogs and wizards can be a pain, but the answer is usually there somewhere.
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 were running Windows Server and Active Directory, so [Microsoft] Azure was a seamless transition. We ran into a few, if any support issues, however, the availability of Microsoft Azure's support team was more than willing and able to guide us through the process. They even proposed solutions to issues we had not even thought of!
We managed to handle most of our problems by looking into Microsoft's official documentation that has everything explained and almost every function has an example that illustrates in detail how a particular functionality works. Just like PowerShell has the ability to show you an example of how some cmdlet works, that is the case also here, and in my opinion, it is a very good practice and I like it.
As I have mentioned before the issue with my Oracle Mismatch Version issues that have put a delay on moving one of my platforms will justify my 7 rating.
Other than SQL taking quite a bit of time to actually install there are no problems with installation. Even on hardware that has good performance SQL can still take close to an hour to install a typical server with management and reporting services.
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.
As I continue to evaluate the "big three" cloud providers for our clients, I make the following distinctions, though this gap continues to close. AWS is more granular, and inherently powerful in the configuration options compared to [Microsoft] Azure. It is a "developer" platform for cloud. However, Azure PowerShell is helping close this gap. Google Cloud is the leading containerization platform, largely thanks to it building kubernetes from the ground up. Azure containerization is getting better at having the same storage/deployment options.
[Microsoft] SQL Server has a much better community and professional support and is overall just a more reliable system with Microsoft behind it. I've used MySQL in the past and SQL Server has just become more comfortable for me and is my go to RDBMS.
For about 2 years we didn't have to do anything with our production VMs, the system ran without a hitch, which meant our engineers could focus on features rather than infrastructure.
DNS management was very easy in Azure, which made it easy to upgrade our cluster with zero downtime.
Azure Web UI was easy to work with and navigate, which meant our senior engineers and DevOps team could work with Azure without formal training.
Increased accuracy - We went from multiple users having different versions of an Excel spreadsheet to a single source of truth for our reporting.
Increased Efficiency - We can now generate reports at any time from a single source rather than multiple users spending their time collating data and generating reports.
Improved Security - Enterprise level security on a dedicated server rather than financial files on multiple laptop hard drives.