17th September 2020: PostgreSQL 13 RC 1 Released!

DB Solo 4.0 Adds Server Comparison and Server Scripting Tools

Posted on 2011-01-18

Nashua, New Hampshire, January 18, 2011 - DB Solo LLC is pleased to announce the general availability of version 4.0 of the DB Solo SQL Query Tool, the latest upgrade to DB Solo's

sophisticated cross-platform Database Query Tool. DB Solo provides developers and administrators with a wealth of advanced features such as visual explain plan, database data & schema

comparison tools, import/export tools and a schema scripting tool.

DB Solo SQL Query Tool is available for Windows, Mac OS X, Linux and Solaris platforms. DB Solo supports all major DBMS products available today, including PostgreSQL and many others.

New Features

New features in version 4.0 include a Server Comparison Tool and Server Scripting Tool. The Server Comparison Tool allows one to compare server-level objects between two separate database servers.

It will report any discrepancies between the servers such as missing or mismatching users, roles, tablespaces and databases.

The Server Scripting Tool allows one to create a DDL script for database server-level objects, such as users, roles and profiles. The generated DDL scripts can then be archived or applied in a different

environment to re-create the objects.

Additionally, this version contains several other enhancements - including support for Windows 7 - and dozens of bug fixes. "These latest features take DB Solo to a level that has never been seen in this price range before", says Marko Hantula, CEO of DB Solo LLC.


DB Solo 4.0 is available for immediate download at http://www.dbsolo.com.

About DB Solo, LLC

DB Solo, LCC is a provider of database development and administration tools for PostgeSQL, SQL Server, Sybase, Oracle, DB2, MySQL, Solid BoostEngine and H2 databases. DB Solo, LLC

was founded in 2004 and is based in Nashua, NH. For more information about DB Solo SQL Query Tool, visit http://www.dbsolo.com.


Marko Hantula

DB Solo, LLC

(603) 557-1134

This post has been migrated from a previous version of the PostgreSQL website. We apologise for any formatting issues caused by the migration.