When comparing DbVisualizer vs SchemaCrawler, the Slant community recommends DbVisualizer for most people. In the question“What are the best relational database design and modelling tools?” DbVisualizer is ranked 5th while SchemaCrawler is ranked 8th. The most important reason people chose DbVisualizer is:
This is a good and stable tool with really good and useful functionality: import/export, SSH tunnelling, fast searching, duplication, DDL visualization etc. If you are a professional, don't complain about the pricing. If you're an amateur, maybe this isn't for you.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Professional tool
This is a good and stable tool with really good and useful functionality: import/export, SSH tunnelling, fast searching, duplication, DDL visualization etc. If you are a professional, don't complain about the pricing. If you're an amateur, maybe this isn't for you.
Pro Duplicate row button
Makes it really easy to stub out example data while developing, just change the values with unique constraints and you have extra data ready to go.
Pro Wildcard finder
Has a search box that will highlight any matching row, regardless of what field is matched (spans multiple columns).
Pro In-line editing
Allows you to edit and save db rows through a spread-sheet like editor.
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 Expensive
License for the full product is costly.
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.