# System Tables, Quotas, And Disaster Recovery

System-table availability and schema, quota limits, and managed disaster-recovery design.

- GA system tables (production-safe): `system.access.audit`, `system.compute.clusters`, `system.compute.node_types`, `system.compute.warehouses`, `system.compute.warehouse_events`, `system.billing.usage`, `system.billing.list_prices`, `system.alert.alerts`, `system.alert.alert_evaluation_history`. PUBLIC PREVIEW tables (not GA): `system.compute.instance_events`, `system.compute.instance_pools`, `system.lakeflow.jobs`, `system.lakeflow.job_tasks`, `system.lakeflow.job_run_timeline`, `system.lakeflow.job_task_run_timeline`, `system.lakeflow.pipelines`, `system.lakeflow.pipeline_update_timeline`, `system.query.history`, `system.access.inbound_network`, `system.access.outbound_network`. The `__databricks_internal` catalog is reserved for Databricks internal state.
- When querying system-table events, use `event_date` for filtering rather than `event_time`; `event_date` partitioning accelerates queries, while `event_time` filtering scans all records and is slower. Incident investigation should use `event_date` ranges to avoid timeout and rate-limit hits.
- Workspace and account quota limits include: 1,000,000 tables per metastore, 10,000 tables per schema, 32,768 columns per table, 10,000 schemas per catalog, 1,000 catalogs per metastore, 1,000 SQL warehouses per workspace, 12,000 simultaneous running tasks, 10,000 jobs per hour, Jobs API 20 requests/second, Workspace API 60 requests/second, MLflow API 120 requests/second. Approaching a limit requires capacity expansion, not workarounds.
- Managed disaster recovery is the recommended approach: it continuously replicates Unity Catalog metadata and managed table data, provides stable failover URLs, and is orchestrated via the account console. DIY DR (manual replication, backup scripts) is not recommended and introduces delay and drift risk.
- Disaster-recovery discipline requires quarterly full failover tests and monthly runbook validation. A DR plan without a test schedule is untested and failure-risky. Failover is a coordinated manual process; automatic failover is not supported.
- Instance pools with minimum-idle instances set a standing-cost floor: minimum-idle instances never terminate, even if autotermination timeout is exceeded. A pool with 10 minimum-idle instances incurs the full compute cost continuously, regardless of job usage. This cost must be explicitly approved and budgeted.
