<?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: SQL Warehouse stuck on &amp;quot;Cluster Start-up Delayed in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/sql-warehouse-stuck-on-quot-cluster-start-up-delayed/m-p/159263#M54805</link>
    <description>&lt;P&gt;This typically points to delayed compute provisioning behind the SQL Warehouse, often due to temporary capacity/resource availability or a transient startup issue.&lt;/P&gt;&lt;P&gt;A few things I would try:&lt;/P&gt;&lt;P&gt;1. Stop and restart the SQL Warehouse&lt;BR /&gt;If it has been stuck for more than 15–30 minutes, manually stop it and start it again.&lt;/P&gt;&lt;P&gt;2. Check Databricks status page&lt;BR /&gt;Confirm whether there is an active incident or degradation in your cloud/region.&lt;/P&gt;&lt;P&gt;3. Try a different warehouse size&lt;BR /&gt;Temporarily switch from Small to Medium and start it again. Sometimes a different size can provision successfully if a specific capacity pool is constrained.&lt;/P&gt;&lt;P&gt;4. Review Events / cluster logs&lt;BR /&gt;Check the warehouse events to see whether the issue is capacity, cloud provider quota, network, policy, or permissions related.&lt;/P&gt;&lt;P&gt;6. Open a Databricks support ticket&lt;BR /&gt;In practice, if a SQL Warehouse is stuck in Starting for more than 20–30 minutes, I would stop/restart first. If it repeats, try resizing or use another warehouse, then raise it with Databricks support.&lt;/P&gt;</description>
    <pubDate>Tue, 16 Jun 2026 21:22:22 GMT</pubDate>
    <dc:creator>rdokala</dc:creator>
    <dc:date>2026-06-16T21:22:22Z</dc:date>
    <item>
      <title>SQL Warehouse stuck on "Cluster Start-up Delayed</title>
      <link>https://community.databricks.com/t5/data-engineering/sql-warehouse-stuck-on-quot-cluster-start-up-delayed/m-p/158221#M54680</link>
      <description>&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;I'm running into an issue with my Starter Warehouse on Databricks and would appreciate any help or pointers.&lt;/P&gt;&lt;P&gt;Problem: My SQL Warehouse has been stuck in a Starting state with the following warning:&lt;/P&gt;&lt;P&gt;Cluster Start-up Delayed. Please wait while we continue to try and start the cluster. No action is required from you.&lt;BR /&gt;cluster-id: 0603-142345-jqh97kz4&lt;/P&gt;&lt;P&gt;It hasn't progressed past this state despite waiting.&lt;/P&gt;&lt;P&gt;Warehouse details:&lt;BR /&gt;- Name: Starter Warehouse (ID: 666b4657765a75b7)&lt;BR /&gt;- Type: Pro&lt;BR /&gt;- Cluster size: Small&lt;BR /&gt;- Scaling: Min 1 / Max 1&lt;BR /&gt;- Auto stop: 60 minutes of inactivity&lt;BR /&gt;- Channel: Current (v 2026.10)&lt;/P&gt;&lt;P&gt;What I've tried so far:&lt;BR /&gt;- Waited for an extended period&lt;BR /&gt;- The warning says no action is required, but the cluster hasn't started&lt;/P&gt;&lt;P&gt;Is this a known intermittent issue with resource availability? Is there a recommended wait time before taking action (e.g., stopping and restarting the warehouse)?&lt;/P&gt;&lt;P&gt;Any advice from the community or Databricks team would be greatly appreciated. Thanks in advance!&lt;/P&gt;</description>
      <pubDate>Wed, 03 Jun 2026 14:59:15 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/sql-warehouse-stuck-on-quot-cluster-start-up-delayed/m-p/158221#M54680</guid>
      <dc:creator>nidhin</dc:creator>
      <dc:date>2026-06-03T14:59:15Z</dc:date>
    </item>
    <item>
      <title>Re: SQL Warehouse stuck on "Cluster Start-up Delayed</title>
      <link>https://community.databricks.com/t5/data-engineering/sql-warehouse-stuck-on-quot-cluster-start-up-delayed/m-p/159263#M54805</link>
      <description>&lt;P&gt;This typically points to delayed compute provisioning behind the SQL Warehouse, often due to temporary capacity/resource availability or a transient startup issue.&lt;/P&gt;&lt;P&gt;A few things I would try:&lt;/P&gt;&lt;P&gt;1. Stop and restart the SQL Warehouse&lt;BR /&gt;If it has been stuck for more than 15–30 minutes, manually stop it and start it again.&lt;/P&gt;&lt;P&gt;2. Check Databricks status page&lt;BR /&gt;Confirm whether there is an active incident or degradation in your cloud/region.&lt;/P&gt;&lt;P&gt;3. Try a different warehouse size&lt;BR /&gt;Temporarily switch from Small to Medium and start it again. Sometimes a different size can provision successfully if a specific capacity pool is constrained.&lt;/P&gt;&lt;P&gt;4. Review Events / cluster logs&lt;BR /&gt;Check the warehouse events to see whether the issue is capacity, cloud provider quota, network, policy, or permissions related.&lt;/P&gt;&lt;P&gt;6. Open a Databricks support ticket&lt;BR /&gt;In practice, if a SQL Warehouse is stuck in Starting for more than 20–30 minutes, I would stop/restart first. If it repeats, try resizing or use another warehouse, then raise it with Databricks support.&lt;/P&gt;</description>
      <pubDate>Tue, 16 Jun 2026 21:22:22 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/sql-warehouse-stuck-on-quot-cluster-start-up-delayed/m-p/159263#M54805</guid>
      <dc:creator>rdokala</dc:creator>
      <dc:date>2026-06-16T21:22:22Z</dc:date>
    </item>
  </channel>
</rss>

