Feature List

Web-based, Browser-based, SaaS-based

  • Do everything supported in SchemaBank (SB) using a modern web browser
  • Enjoy the always-up-to-date application and service
  • Access your data model and schema anytime anywhere
  • Flexible and scalable -- thanks to the web-centric paradigm 

  Visual Data Modeling

  • Draw entity relationship diagrams (ERD) to represent tables, columns, attributes and constraints
  • Support identifying, non-identifying and self relationships
  • Store other database objects: views, stored procedures, trigger functions, etc., into the same project workspace

Forward Engineering

  • Convert your ERD into corresponding SQL statements and create your database according to the design effortlessly 
  • All SQL statements generated respect and support referential integrity
  • Support dropping and cascade dropping (if applicable) of objects before creation

Supported Database

  • MySQL and PostgreSQL as a start
  • Produce brand-specific SQL statements as we understand every brand is different 
  • SQL statements produced run perfectly in your chosen database flavor

Reverse Engineering

  • Import the schema of your already-deployed database into SB for once and manage the schema from the SB side thereafter
  • If you ever suspect there's any change to the schema not initiated via SB, you can always reverse-engineer against your live database anytime and check for changes from SB
  • Support importing SQL backup dump to mitigate the need and the risk of direct access to your database server from SB

Versioning

  • Store your schema in a version repository inside each project
  • Create branches for your version repository for code forking to maintain different releases of your database-related software projects
  • Branches can also be used for developer sandboxes. For instance, each developer having his own branch before commiting his work to the trunk
  • Deployment control of web 2.0 applications can also benefit from branching. Your DBA may want to keep a staging and a production branch separately for stability and quality control.
  • Have as many branches as you like and remove them anytime you want

Change Management

  • Compare versions across branches and generate diff report
  • Refactor your database, whether it's the sandbox or the production machine, using SQL ALTER scripts produced
  • Again, SB-produced SQL scripts are brand-specific and accurate to run at your database 
  • As a good change management practice, version commit is enforced before SQL statements generation

Collaboration

  • Design your database model in a team environment 
  • Share read access to your projects with team members
  • Let team members retrieve a particular version of the schema and work on it further on their own separate environment 
  • Team members can handle change management tasks on their own
  • Allow team members to commit their change to your version repository (i.e. write access), as long as they have sufficient rights 
  • Permit authorised team members to administer the access control for you 
  • Post notes to the project forum for the team to view