dbForge Studio is provided by
Devart and is a universal front-end client for database
management, administration and development. Devart's GUI tool provides
utilities to compare, synchronize, and back up databases (e.g. MySQL, Oracle, SQL Server, PostgreSQL, etc.) with scheduling,
and includes the possibility to analyze and report MySQL tables data. For example, dbForge
Studio for MySQL works with any MariaDB database servers, and supports all
MariaDB objects types. This solution enables users…
$9.95
per month
Pragmatic Workbench (discontinued)
Score 8.5 out of 10
Enterprise companies (1,001+ employees)
Pragmatic Workbench Enterprise was a suite that combined four Pragmatic Works products: BI xPress, DBA xPress, DOC xPress and LegiTest. It was acquired by SentryOne in April 2018, and has reached its EOL phase. After the summer of 2022 it will likely no longer be available, and unsupported.
$2,490
per seat
Pricing
dbForge Studio (Edge)
Pragmatic Workbench (discontinued)
Editions & Modules
Standard (subcription)
$9.95
per month
Professional (subscription)
$19.95
per month
Enterprise (subscription)
$29.95
per month
Standard (subcription)
$99.95
per year
Professional (subscription)
$179.95
per year
Standard
$199.95
Enterprise (subscription)
$229.95
per year
Professional
$349.95
Enterprise
$449.95
Workbench Client Edition
2,490
per seat
Workbench Server Edition
8,995
per server
Workbench Enterprise Edition (Client + Server)
9,995
1 user / 1 server
Offerings
Pricing Offerings
dbForge Studio (Edge)
Pragmatic Workbench (discontinued)
Free Trial
Yes
Yes
Free/Freemium Version
Yes
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
Workbench Enterprise combines all of the functionality within Workbench Client (local install) and Workbench Server (server install).
dbForge Studio (Edge) has much more features than other multi-platform database user interfaces, such as DBeaver or HeidiSQL, and all those features are accessible from a single user interface. SSMS is good only for MS SQL Server, so it's not good for managing multiple RDBM …
Before choosing dbForge Studio I evaluated at least a dozen tools, especially on the Visual Query Builder function. For now, I have identified only one product that has a better Visual Query Builder than dbForge Studio. This other product also manages UNIONs, while dbStudio …
[dbForge Studio for MySQL is] easy to understand and use because it has a sample UI. We can visibly see database tables and their relationships. We can automate queries according to our use and give access according to their use. Not everyone can delete the table or modify it. …
I would say that dbForge equals or beats most of the abilities of the other tools I evaluated at the time. dbForge had better support (Devart), and regular feature updates. dbForge has better tools for data comparison and import/export. The price tag is slightly higher, but …
Prior to dbForge Studio for SQL Server, I have only ever used SQL Server Management Studio to manage SQL Server databases. dbForge software, in my experience, is much easier to use, more intuitive, and hence more productive, speeding up most database-related tasks such as …
Although we had to pay licensing fees to use dbForge, one of the main reasons we chose dbForge is compliance-related: we did not want to use freeware to analyze our database, since we are a utility company that has personally identifiable information in our databases.
We haven't tried any other tools that do comparisons like Data Compare does. Our method prior to buying this tool was to manually run queries on each database and compare the output using text compare or by eye.
While DBeaver ended up being the goto for our development team, everyone else is going to be using dbForge Studio. The UI was hands down much easier to get used to, and the sorting/filtering options make it super easy for anyone to view the data the way they needed it. You …
We found dbForge Studio for Oracle to be more stable and easy to use than both Toad for Oracle and RStudio, among others. There is still room for improvement, such as the MySQL debugger. In the past, we used MySQL Workbench, but the flexibility and robust tool set of dbForge …
I did not make the decision to choose dbForge Studio for SQL Server. I personally like dbForge Studio because of my familiarity with the SQL server and the UI.
We used MySQL Workbench tool before dbForge Studio for MySQL and it did not work well. dbForge Studio for MySQL was a much more complete and flexible solution to resolve our development and administration problems. dbForge Studio for MySQL not only resolved our problems it …
I chose dbForge Studio for MySQL instead of MS SQL Server because: 1) For the most part I don't like Microsoft products. Their UIs are notoriously bad, and you never know when a product tweak will create incompatibilities that will require an expensive upgrade. 2) Since our …
Whenever a user or DBA wants to compare schematics between two environments, dbForge is extremely helpful. This is useful during version or framework upgrades, a database upgrade, patch implementations, service package implementations, or any time to environments would be different. The time it would take to write and execute queries, and then compare is exponentially longer than it takes with dbForge, where this is done and you have an application that allows you to quickly identify incongruities.
Workbench Enterprise is consistent across devices and users so far. It works the same, and access is easy. I have a problem with its security. If you use an enterprise password to access databases, it's very easy to click the show password on the connection page and expose the enterprise password. You shouldn't allow users to use the same accounts to access the database because that means all users are sharing the same password.
[The] installation error I've already reported (ABARTN).xml [could use some improvement]. This has to do with Windows Defender (the default Windows anti-virus) not allowing the installation on the default installation directory of dbForge Studio [for SQL Server], thus the error. [With] the workaround, [I] was to disable the anti-virus for the duration of the installation, then turn it back on when the installation [was] been completed.
[I would like to see] better defined licensing models for larger teams (seated vs. name licenses).
dbForge Studio (Edge) has a great UI and it's versatile, but it still has some glitches. Its multiple database support makes it possible to stick with only one UI to handle different RDBM systems, even though you have to redefine user credentials for each new connection (no copying/cloning feature for database connections). The Edit View and diagramming features also could be improved.
Although experience here is limited, as only one question has been asked and answered promptly, the registration and licensing process was very smooth and professional. There are forums online that discuss dbForge issues, as well as a Facts and Questions section on dbForge's website, so product support does seem to exist if needed.
Our team does the support for us. Sometimes we see download related issues that can easily be fixed by our team. Most issues you will see with one user in your org will probably happen to others, so keep a log and track those issues. Then have a fix for them somewhere that everyone has access to. This will save you a lot of time troubleshooting.
I would say that dbForge equals or beats most of the abilities of the other tools I evaluated at the time. dbForge had better support (Devart), and regular feature updates. dbForge has better tools for data comparison and import/export. The price tag is slightly higher, but renewals rates are pretty good. It's a quality tool that still is well worth the cost.
We perform better and faster syncing analysis between databases.
We update running mysql databases faster and more efficiently.
Especially with MySQL Workbench we had immense irritations due to all the crashes during the day. With dbForge Studio we finally had a power tool which is stable and does not crash constantly.