<?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 Re: Lakebase auto start/stop in Lakebase Discussions</title>
    <link>https://community.databricks.com/t5/lakebase-discussions/lakebase-auto-start-stop/m-p/155784#M99</link>
    <description>&lt;P&gt;&lt;STRONG&gt;Lake base&amp;nbsp;&lt;/STRONG&gt;supports &lt;STRONG&gt;Autoscaling&lt;/STRONG&gt; &amp;amp;&amp;nbsp;&lt;STRONG&gt;Scale to Zero&lt;/STRONG&gt; with Automatic &lt;STRONG&gt;Suspension&lt;/STRONG&gt; &amp;amp; &lt;STRONG&gt;Reactivation&lt;/STRONG&gt; capabilities&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;STRONG&gt;Automatic Suspension&lt;/STRONG&gt;&amp;nbsp;- Lake base compute automatically suspends after a period of inactivity (default is 5 minutes).&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Reactivation&lt;/STRONG&gt;&amp;nbsp;- The compute automatically reactivates within a few hundred milliseconds when you run a new query&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;SPAN&gt;You can use &lt;STRONG&gt;Autoscaling&lt;/STRONG&gt; to adjust resources based on workload demand &amp;amp; &lt;STRONG&gt;scale to zero&lt;/STRONG&gt; to suspend compute entirely after a period of inactivity reducing compute costs to zero during idle periods.&amp;nbsp;You pay only for active compute time &amp;amp; not for idle periods&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;More details &lt;A href="https://docs.databricks.com/aws/en/oltp/projects/scale-to-zero#automatic-suspension" target="_self"&gt;here&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 29 Apr 2026 10:56:01 GMT</pubDate>
    <dc:creator>balajij8</dc:creator>
    <dc:date>2026-04-29T10:56:01Z</dc:date>
    <item>
      <title>Lakebase auto start/stop</title>
      <link>https://community.databricks.com/t5/lakebase-discussions/lakebase-auto-start-stop/m-p/125094#M64</link>
      <description>&lt;P&gt;It doesn’t appear that the Lakebase OLTP instances function like Sql warehouses in the following ways:&lt;BR /&gt;• automatically starting when initiating a connection&lt;BR /&gt;• automatically stopping after no usage in x minutes&lt;/P&gt;&lt;P&gt;I am wondering if others have use cases for auto start-stop, and if it on the product roadmap…&lt;/P&gt;</description>
      <pubDate>Mon, 14 Jul 2025 07:04:31 GMT</pubDate>
      <guid>https://community.databricks.com/t5/lakebase-discussions/lakebase-auto-start-stop/m-p/125094#M64</guid>
      <dc:creator>jericksoncea</dc:creator>
      <dc:date>2025-07-14T07:04:31Z</dc:date>
    </item>
    <item>
      <title>Re: Lakebase auto start/stop</title>
      <link>https://community.databricks.com/t5/lakebase-discussions/lakebase-auto-start-stop/m-p/125120#M65</link>
      <description>&lt;P&gt;I guess that the start/stop pattern is not something you want in a low-latency OLTP database.&lt;BR /&gt;Perhaps they add it in the future.&lt;/P&gt;</description>
      <pubDate>Mon, 14 Jul 2025 08:33:26 GMT</pubDate>
      <guid>https://community.databricks.com/t5/lakebase-discussions/lakebase-auto-start-stop/m-p/125120#M65</guid>
      <dc:creator>-werners-</dc:creator>
      <dc:date>2025-07-14T08:33:26Z</dc:date>
    </item>
    <item>
      <title>Re: Lakebase auto start/stop</title>
      <link>https://community.databricks.com/t5/lakebase-discussions/lakebase-auto-start-stop/m-p/125156#M66</link>
      <description>&lt;P&gt;I can definitely think of use cases where I would trade the cost savings for a few seconds of startup (like serverless sql warehouses), and low-latency thereafter...&lt;/P&gt;</description>
      <pubDate>Mon, 14 Jul 2025 10:33:14 GMT</pubDate>
      <guid>https://community.databricks.com/t5/lakebase-discussions/lakebase-auto-start-stop/m-p/125156#M66</guid>
      <dc:creator>jericksoncea</dc:creator>
      <dc:date>2025-07-14T10:33:14Z</dc:date>
    </item>
    <item>
      <title>Re: Lakebase auto start/stop</title>
      <link>https://community.databricks.com/t5/lakebase-discussions/lakebase-auto-start-stop/m-p/155784#M99</link>
      <description>&lt;P&gt;&lt;STRONG&gt;Lake base&amp;nbsp;&lt;/STRONG&gt;supports &lt;STRONG&gt;Autoscaling&lt;/STRONG&gt; &amp;amp;&amp;nbsp;&lt;STRONG&gt;Scale to Zero&lt;/STRONG&gt; with Automatic &lt;STRONG&gt;Suspension&lt;/STRONG&gt; &amp;amp; &lt;STRONG&gt;Reactivation&lt;/STRONG&gt; capabilities&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;STRONG&gt;Automatic Suspension&lt;/STRONG&gt;&amp;nbsp;- Lake base compute automatically suspends after a period of inactivity (default is 5 minutes).&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Reactivation&lt;/STRONG&gt;&amp;nbsp;- The compute automatically reactivates within a few hundred milliseconds when you run a new query&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;SPAN&gt;You can use &lt;STRONG&gt;Autoscaling&lt;/STRONG&gt; to adjust resources based on workload demand &amp;amp; &lt;STRONG&gt;scale to zero&lt;/STRONG&gt; to suspend compute entirely after a period of inactivity reducing compute costs to zero during idle periods.&amp;nbsp;You pay only for active compute time &amp;amp; not for idle periods&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;More details &lt;A href="https://docs.databricks.com/aws/en/oltp/projects/scale-to-zero#automatic-suspension" target="_self"&gt;here&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 29 Apr 2026 10:56:01 GMT</pubDate>
      <guid>https://community.databricks.com/t5/lakebase-discussions/lakebase-auto-start-stop/m-p/155784#M99</guid>
      <dc:creator>balajij8</dc:creator>
      <dc:date>2026-04-29T10:56:01Z</dc:date>
    </item>
  </channel>
</rss>

