What problem does it solve? After migrating from SQL Server to Databricks, operations teams lose familiar monitoring tools like Query Store, SQL Agent job history, and Resource Governor, leaving them without equivalent visibility into query performance, job execution, and resource consumption. ## Core Features & Use Cases - Monitoring Equivalence Mapping: Maps legacy SQL Server DMVs and tools (Query Store, sysjobhistory, Resource Governor) to Databricks system tables such as system.query.history, system.lakeflow.job_run_timeline, and system.access.audit. - Lakeflow Pipeline Observability: Compares update-level monitoring via system tables against flow-level detail via the event_log TVF or configured event log tables. - Alerts as Code: Defines SQL alerts as versioned resources.alerts in Databricks Asset Bundles with thresholds, cron schedules, and notification destinations (Email, Slack, Teams, PagerDuty). - Performance Tuning Sequence: Applies CLUSTER BY, OPTIMIZE, and ANALYZE with Predictive Optimization for automated Delta table maintenance. - Use Case: After cutover, an operations engineer needs to detect failed migration jobs hourly and compare job success rates against the pre-migration msdb baseline; this Skill provides the exact SQL queries and DAB alert YAML to do so. ## Quick Start Ask the AI to set up post-migration monitoring for Databricks jobs using system tables and create a failure alert as code with Databricks Asset Bundles.