Skip to content
SchemaSmith Learn SchemaSmith
SchemaSmith

Learn SchemaSmith

From your current approach to your first deployment — hands-on, across SQL Server, PostgreSQL, and MySQL.
Start the course Get SchemaSmith SchemaSmith on GitHub

Shape. Strengthen. Succeed.

Start your path

Section titled “Start your path”

From blacksmith vocabulary to running real schema across SQL Server, PostgreSQL, and MySQL — and then operating it like a team. Read the primer, then work the courses in order. Every module pairs a quick concept with a hands-on exercise against a local sandbox: declare your state, quench it to a live database, watch it converge.

Speaking forge A two-minute decoder for SchemaSmith's blacksmith vocabulary. Read this first.
Course 1 · First deployment Six hands-on modules — from why declarative beats migration scripts to bringing an existing database under management. Start here.
Course 2 · Going Deeper Products and deployment guardrails, templates that fan out across schemas and databases, conditional deployment, script tokens, data delivery, and custom properties. Start with product boundaries.
Course 3 · Ship it / operate it The operational arc — team workflow and code review, CI gating, multiple environments, and rollback as a first-class move. Start with what changes when schema-as-code joins a team and a pipeline.
Course 4 · Driving the tools A power-features cookbook — six independent recipes for making custom properties and script tokens drive what SchemaSmith does: environment-aware schema, self-enforcing policy, deploy-time queries, traveling assets, generated DDL, and surviving a destructive rebuild.
Course 5 · Switching to SchemaSmith Coming from Flyway, Liquibase, EF Core, SSDT/DACPAC, or hand-rolled scripts? A tool-by-tool migration cookbook — map your old tool's concepts onto SchemaSmith, then extract your live database into declarative files and walk away from your migration history. Flip to your tool.

What you’ll build

Section titled “What you’ll build”

Not toy examples — real work, on all three engines, against a live sandbox.

  • Your first schema package: one table, declared once, quenched to SQL Server, PostgreSQL, and MySQL.
  • An existing database cast into version-controlled files with SchemaTongs — no hand-written DDL.
  • Multi-tenant fan-out: one quench that finds every database and schema and converges them all.
  • One package, many environments — conditional deployment, script tokens, and data delivery.
  • A real operational loop: code-reviewed schema changes, a CI pipeline, rollback, and zero-downtime promotion across dev, staging, and prod.

What you’ll need

Section titled “What you’ll need”
  • Docker. The labs spin up a throwaway SQL Server + PostgreSQL + MySQL sandbox — start it, work the lab, tear it down.
  • The SchemaSmith CLI on your PATH — schemaquench, schematongs, datatongs. No runtime, no service to configure. Course 1, Module 1 walks the install and confirms the connection.

That’s the whole kit. Read the primer and let’s kindle the forge.