DbVisualizer vs. Microsoft Access

Seamlessly querying PostgreSQL/PostGIS, Oracle, SQL Server, and SQLite from one interface without switching tools. The intelligent autocomplete and schema browsing make it ideal for writing queries and understanding unfamiliar databases. Complex performance tuning, deep monitoring, and automated backup/recovery require specialized DBA tools. Performance degrades with tens or hundreds of thousands of rows; command-line tools or ETL solutions are better suited to bulk data processing.

Incentivized

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.

Incentivized

• Out-of-the-box support for many different databases.
• Intuitive UI for interacting with data.
• Flexibility of SQL Commander for writing scripts.
• Great support for working with JSON data in recent updates.
• Database connections over SSH.
• Table relationship visualization is very helpful.
• The tree view is well organized in how it splits out schemas.

• 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!

Incentivized

• Small, but noticeable: it would be nice to be able to highlight just one column of a data output for copy/paste by clicking on the column header (a feature some of us are accustomed to from SQL Server Management Studio)
• Is there an ability to bulk import an excel file to a table in a connected SQL Server in DbVis? If so, I haven't figured that out yet. I still largely use Microsoft SSMS to import data to our team's personal SQL Server, but can easily query that server via DbVis)
• (I really don't have any major complaints - our company has tried to steer users toward DBeaver for YEARS, which I cannot stand. DbVis knocks the beaver out of the water)

• 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.

Incentivized

We never had problems with it. It is able to connect to all data sources (Oracle, Informix, DB2, SQL Server) that we currently use.

Incentivized

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.

It does what we need it for, which is manipulate data, check connections, visualize database structures, check on user rights, or even just version checks on the used databases. The 'type to get to table name' feature is often irrational in behaviour, which leads to frustration. The start-up time could be much better, and the UI changes between versions are sometimes a hassle for us when buttons are suddenly moved or their appearance changes. We use a wide variety of DBVis versions on customer installations (which use the once-bought version), and differences in the look and feel between versions sometimes slow us down.

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.

Incentivized

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.

Incentivized

Never used

Incentivized

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.

Incentivized

there is no key idea, since it is easy to implement Microsoft Access

[DbVisualizer] is pretty easy to use compared to IntelliJ because of it's simplicity. The performance is very good, it feels as good as a native application compared to the other two softwares I used for the same purpose. It's very cheaper compared to the other two tools and that's a big selling point.

Incentivized

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.

Incentivized

• Positive: Real time saver when working across multiple databases. At least 30-40 mins a day are saved
• Positive: Helpful for the 'quick DBA' tasks without switching to the native tools: approx 1-2 hours saved weekly
• Positive: Easy switch between environments / schemas / etc without hassle: saved at least an hour daily

• 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.

Incentivized