Tracing SQL costs
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-19-2025 12:43 AM
Hello, Databricks community!
In our Account Usage Dashboard, the biggest portion of our costs are labeled simply "SQL".
We want to drill deeper to see where the SQL costs are coming from.
By querying the `system.usage.billing` table we see that it's mostly serverless SQL queries driving the costs. However almost every field in both `product_features`, `usage_metadata`, and `identity_metadata` (even `run_as`) are `null`.
Is this an error or intended behavior? If intended, how can we attribute used DBU quantities to specific queries or users to find out what is driving our costs?
Best regards, Simen