Likelihood to Recommend 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.
Read full review Presto is for interactive simple queries, where
Hive is for reliable processing. If you have a fact-dim join, presto is great..however for fact-fact joins presto is not the solution.. Presto is a great replacement for proprietary technology like
Vertica Read full review Pros Very easy to create entity-relationship diagrams for various tables and designing mock layouts. Really easy to navigate as it hold[s] the classic Microsoft UI. Another good thing is that it comes with the complete MS Office Suite. It is really fast when joining multiple tables no matter what type of join. Works on pretty much same SQL scripts so no need to learn a new language! Read full review Linking, embedding links and adding images is easy enough. Once you have become familiar with the interface, Presto becomes very quick & easy to use (but, you have to practice & repeat to know what you are doing - it is not as intuitive as one would hope). Organizing & design is fairly simple with click & drag parameters. Read full review Cons 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. Read full review Presto was not designed for large fact fact joins. This is by design as presto does not leverage disk and used memory for processing which in turn makes it fast.. However, this is a tradeoff..in an ideal world, people would like to use one system for all their use cases, and presto should get exhaustive by solving this problem. Resource allocation is not similar to YARN and presto has a priority queue based query resource allocation..so a query that takes long takes longer...this might be alleviated by giving some more control back to the user to define priority/override. UDF Support is not available in presto. You will have to write your own functions..while this is good for performance, it comes at a huge overhead of building exclusively for presto and not being interoperable with other systems like Hive, SparkSQL etc. Read full review Likelihood to Renew 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.
Read full review Usability 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.
Read full review Reliability and Availability I don't think the program has ever failed me. It is one of those programs where there is always a solution if you know where to look.
Read full review Support Rating 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.
Read full review Implementation Rating there is no key idea, since it is easy to implement Microsoft Access
Read full review Alternatives Considered 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.
Read full review Presto is good for a templated design appeal. You cannot be too creative via this interface - but, the layout and options make the finalized visual product appealing to customers. The other design products I use are for different purposes and not really comparable to Presto.
Read full review Return on Investment Not having to recreate queries or reports every time you want to use them. Once an item is created and saved as part of the database, you save manpower by not having to recreate them. ROI from a usability standpoint is great. Solid product with great functionality that requires low maintenance usually. Read full review Presto has helped scale Uber's interactive data needs. We have migrated a lot out of proprietary tech like Vertica. Presto has helped build data driven applications on its stack than maintain a separate online/offline stack. Presto has helped us build data exploration tools by leveraging it's power of interactive and is immensely valuable for data scientists. Read full review ScreenShots