<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Databricks SQL Alerts and Jobs Integration: Legacy vs V2 in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/databricks-sql-alerts-and-jobs-integration-legacy-vs-v2/m-p/153053#M53919</link>
    <description>&lt;DIV&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I’m facing a challenge integrating Databricks SQL alerts with a Databricks Job.&lt;/P&gt;&lt;P&gt;After reviewing the documentation, I arrived at the following understanding and would appreciate confirmation from the community or Databricks team:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Legacy SQL alerts cannot be created or managed via DABS.&lt;/LI&gt;&lt;LI&gt;The new &lt;STRONG&gt;SQL Alert task for Jobs&lt;/STRONG&gt; supports only the V2 Databricks SQL alerts, but this feature is currently in &lt;STRONG&gt;Beta&lt;/STRONG&gt; and does not appear to be production‑ready.&lt;/LI&gt;&lt;LI&gt;Legacy alerts are not supported in the new SQL Alert task.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Based on this, I have two questions:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Is there an expected timeline for the SQL Alert task (V2 alerts) to reach Public Preview or GA?&lt;/LI&gt;&lt;LI&gt;Is it recommended/safe to continue using &lt;STRONG&gt;Legacy SQL alerts&lt;/STRONG&gt; (for example, via the SQL task in Jobs) until the V2 Alert task is generally available?&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;Any guidance, best practices, or official recommendations would be greatly appreciated.&lt;/P&gt;&lt;P&gt;Thank you in advance.&lt;/P&gt;&lt;/DIV&gt;</description>
    <pubDate>Thu, 02 Apr 2026 14:22:09 GMT</pubDate>
    <dc:creator>Eliza_geo</dc:creator>
    <dc:date>2026-04-02T14:22:09Z</dc:date>
    <item>
      <title>Databricks SQL Alerts and Jobs Integration: Legacy vs V2</title>
      <link>https://community.databricks.com/t5/data-engineering/databricks-sql-alerts-and-jobs-integration-legacy-vs-v2/m-p/153053#M53919</link>
      <description>&lt;DIV&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I’m facing a challenge integrating Databricks SQL alerts with a Databricks Job.&lt;/P&gt;&lt;P&gt;After reviewing the documentation, I arrived at the following understanding and would appreciate confirmation from the community or Databricks team:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Legacy SQL alerts cannot be created or managed via DABS.&lt;/LI&gt;&lt;LI&gt;The new &lt;STRONG&gt;SQL Alert task for Jobs&lt;/STRONG&gt; supports only the V2 Databricks SQL alerts, but this feature is currently in &lt;STRONG&gt;Beta&lt;/STRONG&gt; and does not appear to be production‑ready.&lt;/LI&gt;&lt;LI&gt;Legacy alerts are not supported in the new SQL Alert task.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Based on this, I have two questions:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Is there an expected timeline for the SQL Alert task (V2 alerts) to reach Public Preview or GA?&lt;/LI&gt;&lt;LI&gt;Is it recommended/safe to continue using &lt;STRONG&gt;Legacy SQL alerts&lt;/STRONG&gt; (for example, via the SQL task in Jobs) until the V2 Alert task is generally available?&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;Any guidance, best practices, or official recommendations would be greatly appreciated.&lt;/P&gt;&lt;P&gt;Thank you in advance.&lt;/P&gt;&lt;/DIV&gt;</description>
      <pubDate>Thu, 02 Apr 2026 14:22:09 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/databricks-sql-alerts-and-jobs-integration-legacy-vs-v2/m-p/153053#M53919</guid>
      <dc:creator>Eliza_geo</dc:creator>
      <dc:date>2026-04-02T14:22:09Z</dc:date>
    </item>
    <item>
      <title>Re: Databricks SQL Alerts and Jobs Integration: Legacy vs V2</title>
      <link>https://community.databricks.com/t5/data-engineering/databricks-sql-alerts-and-jobs-integration-legacy-vs-v2/m-p/153222#M53947</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/225470"&gt;@Eliza_geo&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;Given your Unity Catalog + serverless + DABS environment, here's what makes sense right now:&lt;/P&gt;&lt;P&gt;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.&lt;BR /&gt;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.&lt;BR /&gt;Watch the release notes: The Databricks release notes are updated frequently.&amp;nbsp;&lt;BR /&gt;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.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 03 Apr 2026 17:57:00 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/databricks-sql-alerts-and-jobs-integration-legacy-vs-v2/m-p/153222#M53947</guid>
      <dc:creator>lingareddy_Alva</dc:creator>
      <dc:date>2026-04-03T17:57:00Z</dc:date>
    </item>
  </channel>
</rss>

