When comparing DbForge Studio for PostgreSQL vs SchemaCrawler, the Slant community recommends SchemaCrawler for most people. In the question“What are the best database design programs?” SchemaCrawler is ranked 9th while DbForge Studio for PostgreSQL is ranked 12th. The most important reason people chose SchemaCrawler is:
The text-based output serves for database documentation, and is designed to be diff-ed against other database schemas.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Advanced code completion features
Prompting the names of existing materialized views, as well as context prompting of database objects
Pro Query Profiler
Helpful diagrams of query execution, and also the list of operations that takes place on the server
Pro Data Editor
The data can be edited in the same way as with Google Sheets/MS Excel or in the card view mode.
Pro High execution speed
Downloading the main_ExceptionFrames.sql file of 100 Mb in size ~ 1 min
Pro SQL Code Formatter
Automatic formatting of SQL Code based on user-chosen code styles
Pro Data Export/Import
10+ file format support, including Google Sheets
Pro Master-Detail Browser
The 'design view' for setting up relations between tables, smart sorting, and filtering
Pro Code complition
Prompting keywords for functions etc.
Pro Cached update mode in Data Editor
Allows to control data editing within database objects
Pro Generate Script AS feature
Allows generating a script for the CREATE statements for specific database objects (views, materialized views, triggers, functions, procedures)
Pro Object Explorer
Provides a quick navigation through the object tree
Pro File format support
Dozen of file formats are supported, including Google sheets.
Pro Many options for output formats in addition to graphical
The text-based output serves for database documentation, and is designed to be diff-ed against other database schemas.
Pro Extensive and detailed documentation online
Including visuals of the results of command-line option usage.
Pro Free
Cons
Con Data export
Data export does an individual insert per row of data, which is a little inefficient.
Con Need Java
Con Does not work with schema dumpfiles
SchemaCrawler has no methods for dealing with when you only have a schema generated via something like (mysqldump --no-data [options] >schema-only_dump.sql) , and do not currently have access to a live database to connect with.