When comparing Schemaball vs pgModeler, the Slant community recommends pgModeler for most people. In the question“What are the best relational database design and modelling tools?” pgModeler is ranked 10th while Schemaball is ranked 13th. The most important reason people chose pgModeler is:
Can generate scripts to synchronize a database.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Supports reading schemas from multiple sources
Schemaball can read schemas from multiple sources such as SQL schema dumps, flat files or live databases.

Pro Interesting twist on visual interface
Gives a quick way to grasp an overview on the past/present complexity of the database (or group of tables) undergoing inspection.
Pro Diff scripts
Can generate scripts to synchronize a database.
Pro Reverse engineering
Can generate diagrams from an existing database.
Pro Export formats
Can export to SQL script file, PNG, SVG or directly to PostgreSQL.
Cons
Con Visualizations may be hard to get used to
Since schemas are visualized by using stylized "schema balls" it may be hard getting used to them since they are so different from the other, more straightforward options.
Con Compiling
Can't be compiled in Microsoft Visual Studio because of gcc/clang extensions.
Instructions on how to compile for Windows.
