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
Redgate SQL Toolbelt Essentials
Score 8.2 out of 10
N/A
Redgate's SQL Toolbelt Essentials includes industry-standard tools for SQL Server development & deployment, enabling users to include SQL Server databases in agile processes and enabilng developers to embed robust and scalable development practices.
N/A
Pricing
dbForge Studio (Edge)
Redgate SQL Toolbelt Essentials
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
No answers on this topic
Offerings
Pricing Offerings
dbForge Studio (Edge)
Redgate SQL Toolbelt Essentials
Free Trial
Yes
Yes
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
dbForge Studio (Edge)
Redgate SQL Toolbelt Essentials
Considered Both Products
dbForge Studio (Edge)
Verified User
Anonymous
Chose dbForge Studio (Edge)
dbForge [Studio for SQL Server] is far superior in its features, capabilities, ease [of] use, menu layout, and sophisticated design.
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 …
I've used Visual Studio Database Projects for this type of work in the past with some success, but Redgate SQL Compare is faster, more transparent, and simply easier to use. Faster is self explanatory. More transparent, means that it's much easier to set up your desired options …
I was familiar with the quality of Redgate's products at the time of making the purchase decision. I checked out a trial version to make sure I could achieve what I wanted from the application, but I never made comparisons with other vendors tools on this occasion. …
Honestly, I have never been interested in the usable alternatives. I have always been good to use it. The license cost after all has always been sustainable. I never had the idea of \ u200b \ u200bchanging it nor the need to look at other software. Also (always a redgate …
We have used Symantecs Database Agents for Backup Exec and Veeam's Database Backup products. Symantec does not stack up well as compared to Redgate. Veeam is a considerable contender with their SQL Server Explorer. In some scenarios I would prefer to use VEEAM over Redgate, …
Frankly, I came into a RedGate equipped database shop and never considered looking for anything else. I didn't find RedGate, it found me. When I leave one company, to go to a new company I immediately make sure there are licenses to Toolbelt Essentials. It's that important to …
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.
We use SQL Compare to troubleshoot performance problems quite a bit since our data model is more like a template and not everything is 100% in sync and customization occurs between different client databases. We continually get pulled into performance issues and the developers will say Client A is performing different than Client B, why? Using SQL Compare, we usually find that one client was tuned and had indexes altered or added that weren't deployed to all clients or other objects weren't deployed correctly during the release. On the other hand, since our data model practices allow client databases to drift I tried to create a new golden image by trying to compare multiple databases based on the same data model and found it to be a very difficult process to complete using SQL Compare. SQL Compare gave me too much information and doesn't allow enough filtering to eliminate a lot of the noise.
Simple and easy comparison of database schemas and data. Differences can be copied or synced from one database to another with a click of a button.
You can save "projects" so that you can easily rerun a previous comparison whenever you need to.
It has a very simple, easy to learn interface. I've never needed to read any documentation or watch any tutorials in order to figure out how to do something.
[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).
Pricing.... I wish there was an inexpensive developer version I could buy for myself.
Portability.... I would like to use it from a flash drive so I can use it where ever I am asked to work.
Unbundled.... This may be available already but I dont' recall I can buy it cheaply as a stand-alone product. Its only part of the bundle - cost effectively.
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.
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.
I've used Visual Studio Database Projects for this type of work in the past with some success, but Redgate SQL Compare is faster, more transparent, and simply easier to use. Faster is self explanatory. More transparent, means that it's much easier to set up your desired options for schema change deployment scripts. Easier to use, It's really dead simple. Start a project, connect your source, connect destination, click compare.
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.