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
Azure SQL Database
Score 8.3 out of 10
N/A
Azure SQL Database is Microsoft's relational database as a service (DBaaS).
Microsoft Access is used independently of Microsoft's Office suite (also in use) at our company - the usual applications: Word, Excel, Outlook, etc. and does not really overlap. Microsoft Access was selected as a simple, functional inventory database based on ease of data …
Microsoft Access is a superb software in database management system. I have been using it for many years without any hesitations. The software is making it different from other software with its awesome features. The software is cost effective for the organisation. It also …
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 …
With [Microsoft] Access I am able to quickly create simple database driven solutions with built in UI and reporting in one tool. Advanced coding is not necessary and the tool guides you through building out. Opponents for a robust, end-to/end product.
Having used Snowflake, I can definitely say that both of these tools are very easy to use and value for money. Although for me, the aspects where Microsoft Access stacks up are its low cost and usability. Snowflake is good with its cloud-based system but for startups where the …
I haven't really used another database product other than Microsoft Access since the mid-90s. I don't even remember which program I did use, but needless to say, it did not have as much functionality nor was it as user friendly as databases today. So I really can't say how …
Crystal is easier for report writing, but isn't a database solution. Salesforce is lovely, but much more expensive than an old copy of Microsoft Office. For a small budget, [Microsoft] Access was really the only viable option. I only wish it was easier to write complex reports.
[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 …
Microsoft Access is better for large files and backlogs than Excel because it can handle the workload. Excel is great as well, but filtering and searching is limited, and it can crash rather easily. You don't see those problems with Access.
We've actually started to use both of these programs. There are pros and cons to both. Microsoft Access is best for linking two sets of data that already have a common shared field (i.e. both sets of data include a student ID number, social security number, etc) Airtable is best …
SharePoint is good for simple data structures, use of workflow, integration with AD, etc. But SharePoint does not support fully relational data or complex reporting, whereas Access absolutely does.
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.
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 …
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 …
MS SQL is a more powerful tool but I love the reporting feature in MS Access. MS Excel is useful for complex calculations but to me, MS Access helps me organize that data. InfoPath is similar to MS Access in that you can create forms for data entry, but it does not include …
Better and more useful automation tools are available. Better at scaling and hosting your data. Greater security around access of data and encrypting where required. Allows for seamless integration in other Azure solutions which allows for greater flexibility when using the …
Depending on the use case they stack up very well. Google and AWS are well suited multi-cloud strategies or those that need a high level of RDS performance.
Mainly response time. Azure SQL Database is very fast and very reliable when it comes to executing queries and gathering the data results. Also, the exporting options it gives are far exceeding expectations and enable users to accommodate any deliverable in a timely and …
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 …
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.
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 …
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 …
Director, eCommerce Analytics and Digital Marketing
Chose Azure SQL Database
The Azure SQL Database, compared to our on premise SQL server installation, is much easier to use in terms of seeing database diagnostics. There is a whole visualization platform that comes with the tool that will allow your database administrator to see what jobs are tying up …
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.
Being able to manage our databases in the cloud, scale quickly, and only require access to VMs made choosing Azure a no-brainer over a traditional SQL Server installation/integration. We don't have the budget or resources to integrate and maintain servers on our own, so using …
I would say MySQL in either Aurora or MariaDB form come close however, Azure SQL Database has a more streamlined approach to delivering a consistent programmability model, supported drivers and feature set.
Azure SQL Database T-SQL is advantageous and more complete than SQL …
Azure owned by Microsoft who owned SQL Server, so provided a variety of tools for easy migration/transition and from on-premises to the cloud; and management. I recommend using Azure for any on-prem SQL server databases.
Azure SQL is a clear upgrade to SQL Server 2012 and pretty much has the advantage with all the extra features that it has. Security, queries, exporting tables, T-SQL has all improved. Transitioning 18+ years of an in-house database to the cloud was a struggle, but for the …
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 …
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.
Comparing with Amazon Aurora: Azure SQL DB is 100% compatible with SQL Server and Aurora is compatible with MySQL and PostGreSQL. Because of if, SQL DB suits large enterprises with hundreds of databases better. Comparing with Oracle: the main issue is that Oracle will try to …
It stacks up in different ways, for the most part, I think Microsoft is doing a really good job versus the competition. They basically started database type products from the beginning. I've always been excited about updates and can see their progress over time. Get's me really …
Microsoft Access can be easily implemented with training. It doesn't require expert level skill for basic reporting functions - but can be scaled to a complex database with sophisticated users. Its appropriate to consider if excel needs to be used to create reports, or if there are data entry needs - with corresponding reports.
Your upcoming app can be built faster on a fully managed SQL database and can be moved into Azure with a few to no application code changes. Flexible and responsive server less computing and Hyperscale storage can cope with your changing requirements and one of the main benefits is the reduction in costs, which is noticeable.
Scalability is #1: if it used to be an almost no-win endeavour to try to modernize your server or migrate to other hardware, with Azure SQL Database it becomes a press of a button.
All the tools simply work after you are on Azure SQL Database.
The applications do not need changes in order to start using Azure SQL Database.
Hybrid Cloud scenarios will work.
Clustering and failover - already there.
You can start monitoring the use and extract performance insights in a new way in Azure.
A little slow on processing complex or large Views. We use a lot of Views to feed our BI system, and the processing time could see some improvement, IMHO.
Additional monitoring components would be nice too, automating some built in performance measurement tools would be a nice feature.
Price can always be improved as well. It’s not bad, but room for improvement.
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.
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.
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.
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 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.
Microsoft Access is used independently of Microsoft's Office suite (also in use) at our company - the usual applications: Word, Excel, Outlook, etc. and does not really overlap. Microsoft Access was selected as a simple, functional inventory database based on ease of data entry, search functionality and avoiding the need for a separate ERP module.
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 them, Azure SQL is the right size.