Platform
Database
Fabric Experiments targets standard Postgres; Databricks Lakebase is the Fabric-managed hosted path.
The database stance is Postgres-first.
Fabric-managed environments run on Databricks Lakebase Postgres via DATABASE_PROVIDER=databricks-lakebase (see Databricks deployment). The migrations also run against standard Postgres providers such as Neon, RDS Postgres, Cloud SQL Postgres, Supabase Postgres, Crunchy, or local/Testcontainers Postgres.
Migrations
Migrations are provider-neutral Postgres migrations. They live in infra/neon/migrations (the directory name is historical):
001_fx_initial.sql002_better_auth.sql003_manifest_keys.sql004_audit_exports.sql005_idempotency.sql006_audit_export_cursor_id.sql007_billing_ledger.sql008_byok_config.sql009_event_retention.sql010_audit_forward_cursor.sql011_preview_secrets.sql012_api_keys.sql013_rename_org_to_tenant.sql014_workspace_resources.sql015_test_runs.sql016_enterprise_identity.sql017_scim_group_provisioning.sql018_governance_settings.sql019_datasets_evals.sql020_eval_run_outbox.sql022_traces.sql(021is intentionally unused)023_ingest_tokens.sql024_prompts_playground.sql025_stripe_webhook_state.sql
Apply them in order for every new environment.
for f in infra/neon/migrations/*.sql; do
psql "$DATABASE_URL" -f "$f"
done