Databricks SQL Alerts and Jobs Integration: Legacy vs V2

[Eliza_geo]

Hi,

I’m facing a challenge integrating Databricks SQL alerts with a Databricks Job.

After reviewing the documentation, I arrived at the following understanding and would appreciate confirmation from the community or Databricks team:

• Legacy SQL alerts cannot be created or managed via DABS.
• The new SQL Alert task for Jobs supports only the V2 Databricks SQL alerts, but this feature is currently in Beta and does not appear to be production‑ready.
• Legacy alerts are not supported in the new SQL Alert task.

Based on this, I have two questions:

1. Is there an expected timeline for the SQL Alert task (V2 alerts) to reach Public Preview or GA?
2. Is it recommended/safe to continue using Legacy SQL alerts (for example, via the SQL task in Jobs) until the V2 Alert task is generally available?

Any guidance, best practices, or official recommendations would be greatly appreciated.

Thank you in advance.

[lingareddy_Alva]

Hi @Eliza_geo ,

Given your Unity Catalog + serverless + DABS environment, here's what makes sense right now:

For new pipelines: Stick to legacy SQL alerts invoked via a SQL task in Jobs. Avoid the SQL Alert task (Beta) in production workflows — Beta features can have breaking changes between releases.
For DABS management of alerts: Use the legacy Alerts API (/api/2.0/preview/sql/alerts) directly in a notebook or Python task within your job to create/manage alerts programmatically, since DABS + V2 alert + SQL task is a broken triangle right now.
Watch the release notes: The Databricks release notes are updated frequently. 
Flag it with your account team: If this is blocking a production design decision, your Databricks TAM or AE can give you a non-public roadmap signal i think.