DbVisualizer vs. Microsoft Visual Studio Code

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 general workhorse IDE, Microsoft Visual Studio Codee is unmatched. Building on the early success of applications such as Atom, it has long been the standard for electron based IDEs. It can be outshone using IDEs that are dedicated to particular platforms, such as Microsoft Visual Studio Code for .net and the Jetbrains IDEs for Java, Python and others. For remote collaborative development, something like Zed is ahead of VSCode live share, which can be quite flakey.

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.

• Integrate with the git repository very well.
• Integrated copilot chat is very helpful to write code snippets and helps beginners to start with coding and development.
• Great library of available extensions is one of the best features in Microsoft Visual Studio Code.
• Dedicated Testing option to configure pytest and others are quite handy to use.

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)

• The customization of key combinations should be more accessible and easier to change
• The auxiliary panels could be minimized or as floating tabs which are displayed when you click on them
• A monitoring panel of resources used by Microsoft Visual Studio Code or plugins and extensions would help a lot to be able to detect any malfunction of these

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

Solid tool that provides everything you need to develop most types of applications. The only reason not a 10 is that if you are doing large distributed teams on Enterprise level, Professional does provide more tools to support that and would be worth the cost.

Incentivized

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 Visual Studio Code earns a 10 for its exceptional balance of power and simplicity. Its intuitive interface, robust extension ecosystem, and integrated terminal streamline development. With seamless Git integration and highly customizable settings, it adapts perfectly to any workflow, making complex coding tasks feel effortless for beginners and experts alike.

Incentivized

Overall, Microsoft Visual Studio Code is pretty reliable. Every so often, though, the app will experience an unexplained crash. Since it is a stand-alone app, connectivity or service issues don't occur in my experience. Restarting the app seems to always get around the problem, but I do make sure to save and backup current work.

Incentivized

Microsoft Visual Studio Code is pretty snappy in performance terms. It launches quickly, and tasks are performed quickly. I don't have a lot of integrations other than CoPilot, but I suspect that if the integration partner is provisioned appropriately that any performance impact would be pretty minimal. It doesn't have a lot of bells and whistles (unless you start adding plugins left and right).

Incentivized

Never used

Incentivized

Active development means filing a bug on the GitHub repo typically gets you a response within 4 days. There are plugins for almost everything you need, whether it be linting, Vim emulation, even language servers (which I use to code in Scala). There is well-maintained official documentation. The only thing missing is forums. The closest thing is GitHub issues, which typically has the answers but is hard to sift through -- there are currently 78k issues.

Incentivized

[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

Visual Studio Code stacks up nicely against Visual Studio because of the price and because it can be installed without admin rights. We don't exclusively use Visual Studio Code, but rather use Visual Studio and Visual Studio code depending on the project and which version of source control the given project is wired up to.

Incentivized

It is easily deployed with our Jamf Pro instance. There is actually very little setup involved in getting the app deployed, and it is fairly well self-contained and does not deploy a large amount of associated files. However, it is not particularly conducive to large project, multi-developer/department projects that involve some form of central integration.

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

• Saves money by replacing suites of tools such as Visual Studio, IntelliJ, etc.
• Speeds development time and developer environment setup time
• Strengthens code quality with integrated autoformatting and linting
• Strengths Git practices by keeping version control tightly connected with the code

Incentivized