dbForge Studio (Edge) vs. Apache Derby vs. RaimaDB

This tool is useful for small and large IT departments and associated data analysts that perform direct database functions such as DBA tasks or extracting/importing data. Non-technical staff members would not benefit from this tool as much as the functions are detailed and technical. However, automation engineers will find this tool very open for automation, and can generate the scripting code for any of its functions.

Incentivized

If you need a SQL-capable database-like solution that is file-based and embeddable in your existing Java Virtual Machine processes, Apache Derby is an open-source, zero cost, robust and performant option. You can use it to store structured relational data but in small files that can be deployed right alongside with your solution, such as storing a set of relational master data or configuration settings inside your binary package that is deployed/installed on servers or client machines.

Incentivized

Works very well in applications designed for IoT devices where performance and footprint are of great importance.

• Connection manager (we use it through ssh tunnels) works effortlessly.
• Great sync tools for both database schemas and data.
• Storing code snippets to be used when needed.
• Nice code suggestions while typing queries.
• Usually does very well with storing your session and opening all of your sql tabs when opening the apps next time.
• Does very well when executing large sql files (without opening the files into the application that is).
• Pretty good debugging help when a problem occurs in executing a query or a files with multiple queries.

Incentivized

• Apache Derby is SMALL. Compared to an enterprise scale system such as MSSQL, it's footprint is very tiny, and it works well as a local database.
• The SPEED. I have found that Apache Derby is very fast, given the environment I was developing in.
• Based in JAVA (I know that's an obvious thing to say), but Java allows you to write some elegant Object Oriented structures, thus allowing for fast, Agile test cases against the database.
• Derby is EASY to implement and can be accessed from a console with little difficulty. Making it appropriate for everything from small embedded systems (i.e. just a bash shell and a little bit of supporting libraries) to massive workstations.

Incentivized

• First of all the performance of RDM was superior compared to SQLite in my multi-user environment (about 200 users). The pricing was surprisingly good compared to other high-performance databases.
• Decreased time to market, a faster and more performant application overall and lower maintenance costs.
• They run on most RTOS and can be used in a cross-platform environment.

• The ability to parameterize searches more would be advantageous. For example, being able to specify to only look for certain columns, certain data type changes, etc.
• The output reports from dbForge are very plain and could contain more detail, and perhaps be structured more like a pivot table form Excel

Incentivized

• It may not scale as well as some more mature database products.
• Used it primarily from the command line with openjpa and jdbc, and from third-party clients such as Squirrel.
• May benefit by providing more sophisticated tools to optimize query performance.

Incentivized

• I would like to see REST API with a GUI for administration

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.

Incentivized

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 still doesn't do it visually. However, the better alternative product is enormously slower in operations and less feature-rich than DbForge Studio

SQLite is another open-source zero-cost file-based SQL-capable database solution and is a good alternative to Apache Derby, especially for non-Java-based solutions. We chose Apache Derby as it is Java-based, and so is the solution we embedded it in. However, SQLite has a similar feature set and is widely used in the industry to serve the same purposes for native solutions such as C or C++-based products.

Incentivized

RDM performs way better than SQLite when the database is larger and has multiple users.

• Saved a TON of time when looking at massive amounts of parent/child data by allowing us to just use the master-detail browser.
• Very little training time needed for employees that are already used to using SQL Management Studio. This is a proper Windows UI application.
• Very cost effective to purchase the standard edition for every employee that needs it, but the free edition does most of what they need too!

Incentivized

• Being Open source, the resources spent on the purchase of the product are ZERO.
• Contrary to popular belief, open source software CAN provide support, provided that the developers/contributors are willing to answer your emails.
• Overall, the ROI was positive: being able to experiment with an open source technology that could perform on par with the corporate products was promising, and gave us much information about how to proceed in the future.

Incentivized

• Decreased time to market
• Decreased maintenance and service costs on hardware.