<?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 Predictive Optimization keeps running on system.lakebase after disabling it at account level in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/predictive-optimization-keeps-running-on-system-lakebase-after/m-p/176816#M57212</link>
    <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;On an Azure Databricks workspace (Premium, Southeast Asia) that uses Lakebase, Predictive Optimization started running on 16 Nov 2026 on the Databricks-managed telemetry tables in system.lakebase (postgres_logs, compute_counters, plan_history and 7 others). It runs VACUUM, DELETE and PURGE every day and is billed as billing_origin_product = PREDICTIVE_OPTIMIZATION (SKU PREMIUM_JOBS_SERVERLESS_COMPUTE). We have no tables of our own that use it.&lt;/P&gt;&lt;P&gt;What we tried:&lt;BR /&gt;1. Disabled Predictive Optimization at account level (Account Console &amp;gt; Settings &amp;gt; Feature enablement). The metastore and the system catalog now show DISABLE.&lt;BR /&gt;2. But the schema system.lakebase still has enable_predictive_optimization = ENABLE set explicitly, and its tables inherit it. Operations kept running after the change (per system.storage.predictive_optimization_operations_history).&lt;BR /&gt;3. ALTER SCHEMA system.lakebase DISABLE PREDICTIVE OPTIMIZATION and the Unity Catalog API (schemas update) both fail with: PERMISSION_DENIED: Predictive optimization can't be modified on a system schema.&lt;/P&gt;&lt;P&gt;Usage so far: 2.58, 4.08 and 1.72 DBU per day. Small, but for a small R&amp;amp;D account it is the largest item on the bill.&lt;/P&gt;&lt;P&gt;Questions:&lt;BR /&gt;- Is there a supported way to turn Predictive Optimization off for system.lakebase, or to make it honour the account-level setting?&lt;BR /&gt;- Is this maintenance of system telemetry tables expected to be billed to the customer?&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
    <pubDate>Thu, 19 Nov 2026 03:26:35 GMT</pubDate>
    <dc:creator>trantu</dc:creator>
    <dc:date>2026-11-19T03:26:35Z</dc:date>
    <item>
      <title>Predictive Optimization keeps running on system.lakebase after disabling it at account level</title>
      <link>https://community.databricks.com/t5/data-engineering/predictive-optimization-keeps-running-on-system-lakebase-after/m-p/176816#M57212</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;On an Azure Databricks workspace (Premium, Southeast Asia) that uses Lakebase, Predictive Optimization started running on 16 Nov 2026 on the Databricks-managed telemetry tables in system.lakebase (postgres_logs, compute_counters, plan_history and 7 others). It runs VACUUM, DELETE and PURGE every day and is billed as billing_origin_product = PREDICTIVE_OPTIMIZATION (SKU PREMIUM_JOBS_SERVERLESS_COMPUTE). We have no tables of our own that use it.&lt;/P&gt;&lt;P&gt;What we tried:&lt;BR /&gt;1. Disabled Predictive Optimization at account level (Account Console &amp;gt; Settings &amp;gt; Feature enablement). The metastore and the system catalog now show DISABLE.&lt;BR /&gt;2. But the schema system.lakebase still has enable_predictive_optimization = ENABLE set explicitly, and its tables inherit it. Operations kept running after the change (per system.storage.predictive_optimization_operations_history).&lt;BR /&gt;3. ALTER SCHEMA system.lakebase DISABLE PREDICTIVE OPTIMIZATION and the Unity Catalog API (schemas update) both fail with: PERMISSION_DENIED: Predictive optimization can't be modified on a system schema.&lt;/P&gt;&lt;P&gt;Usage so far: 2.58, 4.08 and 1.72 DBU per day. Small, but for a small R&amp;amp;D account it is the largest item on the bill.&lt;/P&gt;&lt;P&gt;Questions:&lt;BR /&gt;- Is there a supported way to turn Predictive Optimization off for system.lakebase, or to make it honour the account-level setting?&lt;BR /&gt;- Is this maintenance of system telemetry tables expected to be billed to the customer?&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Thu, 19 Nov 2026 03:26:35 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/predictive-optimization-keeps-running-on-system-lakebase-after/m-p/176816#M57212</guid>
      <dc:creator>trantu</dc:creator>
      <dc:date>2026-11-19T03:26:35Z</dc:date>
    </item>
  </channel>
</rss>

