# Databricks SQL Warehouse on AWS | ZopNight

> Every check ZopNight runs on your Databricks SQL Warehouse on AWS: 3 in total, across governance, orphaned resources and scheduling.

Source: https://zop.dev/zopnight/rules/aws/databricks-sqlwarehouse

---

_AWS · 3 checks_

## Databricks SQL Warehouse on AWS, checked for you.

ZopNight runs 3 checks on your Databricks SQL Warehouse in AWS, covering governance, orphaned resources and scheduling. It can also stop them outside working hours and start them again on schedule.

- 3 — checks
- 3 — categories
- Manual — fixes, spelled out
- Yes — can be scheduled

Free to start. No card. The playground just needs your work email.

## Every check, grouped by what it protects.

Each one opens with why it matters and exactly what to change.

### Orphaned resources

Resources no longer attached to anything that needs them, such as unattached volumes and unassigned IPs.

- [Orphaned SQL Warehouse (No Queries in 30 Days)](https://zop.dev/zopnight/rules/orphaned-sql-warehouse-no-queries-in-30-days)

### Scheduling

Resources running 24x7 with a clear off-hours usage pattern, ready for start and stop scheduling.

- [SQL Warehouse Auto-Stop Disabled/Excessive](https://zop.dev/zopnight/rules/sql-warehouse-auto-stop-disabled-excessive)

### Governance

Missing tags and labels that break cost attribution, such as no environment, team or cost-centre value.

- [Missing Cost-Allocation Tags](https://zop.dev/zopnight/rules/missing-cost-allocation-tags)

## Find these on your own Databricks SQL Warehouse.

Connect a read-only role and ZopNight inventories the Databricks SQL Warehouse you run, then runs all 3 checks against them.

[object Object]