<?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 SQL Warehouse Configuration Tweaking in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/sql-warehouse-configuration-tweaking/m-p/11146#M6174</link>
    <description>&lt;P&gt;I'm new to setting up a DB environment, and have accumulated a couple of questions around configuring a SQL Warehouse&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. When creating a SQL warehouse, the smallest size is 2X-Small, which is 4DBU.  The pricing calculator (for Azure) implies you can configure this down to as a little as 0.75DBU, but that's not an option within Databricks.  Is this correct?  Is it correct that can I create a All-Purpose Compute cluster at 0.75DBU, but not a SQL Cluster?  FWIW, I'm wanting to implement a couple of very small clusters for dev/test.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. The Azure pricing calculator also implies you can configure the specific hardware used for your SQL Clusters.  Within Databricks itself, this doesn't seem configurable.  Monitoring our Azure environment, it seems that Databricks spawns E8ds_v4 Virtual Machines when I switch on a SQL cluster, but I have no control over that.  If I want to take advantage of Azure reserved pricing, is there any mechanism to ensure Databricks uses the hardware that I've reserved?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 19 Jan 2023 23:35:10 GMT</pubDate>
    <dc:creator>najmead</dc:creator>
    <dc:date>2023-01-19T23:35:10Z</dc:date>
    <item>
      <title>SQL Warehouse Configuration Tweaking</title>
      <link>https://community.databricks.com/t5/data-engineering/sql-warehouse-configuration-tweaking/m-p/11146#M6174</link>
      <description>&lt;P&gt;I'm new to setting up a DB environment, and have accumulated a couple of questions around configuring a SQL Warehouse&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. When creating a SQL warehouse, the smallest size is 2X-Small, which is 4DBU.  The pricing calculator (for Azure) implies you can configure this down to as a little as 0.75DBU, but that's not an option within Databricks.  Is this correct?  Is it correct that can I create a All-Purpose Compute cluster at 0.75DBU, but not a SQL Cluster?  FWIW, I'm wanting to implement a couple of very small clusters for dev/test.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. The Azure pricing calculator also implies you can configure the specific hardware used for your SQL Clusters.  Within Databricks itself, this doesn't seem configurable.  Monitoring our Azure environment, it seems that Databricks spawns E8ds_v4 Virtual Machines when I switch on a SQL cluster, but I have no control over that.  If I want to take advantage of Azure reserved pricing, is there any mechanism to ensure Databricks uses the hardware that I've reserved?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 19 Jan 2023 23:35:10 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/sql-warehouse-configuration-tweaking/m-p/11146#M6174</guid>
      <dc:creator>najmead</dc:creator>
      <dc:date>2023-01-19T23:35:10Z</dc:date>
    </item>
    <item>
      <title>Re: SQL Warehouse Configuration Tweaking</title>
      <link>https://community.databricks.com/t5/data-engineering/sql-warehouse-configuration-tweaking/m-p/11147#M6175</link>
      <description>&lt;P&gt;&lt;A href="https://learn.microsoft.com/en-us/azure/databricks/sql/admin/sql-endpoints#cluster-size" alt="https://learn.microsoft.com/en-us/azure/databricks/sql/admin/sql-endpoints#cluster-size" target="_blank"&gt;Docs&lt;/A&gt; do show that it uses E8d as you wrote.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SQL Warehouses are a different type of compute than All Purpose or Jobs clusters.  The SQL warehouses always use Photon.  All purpose and Jobs clusters are used for things such as notebooks or Delta Live Tables and that's the 0.75DBU pricing you're seeing.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The azure pricing calculator &lt;A href="https://azure.microsoft.com/en-us/pricing/calculator/" alt="https://azure.microsoft.com/en-us/pricing/calculator/" target="_blank"&gt;here&lt;/A&gt; has our logo from 3 years ago on it, so I wouldn't put much faith in it.  &lt;/P&gt;</description>
      <pubDate>Fri, 20 Jan 2023 00:56:14 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/sql-warehouse-configuration-tweaking/m-p/11147#M6175</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2023-01-20T00:56:14Z</dc:date>
    </item>
    <item>
      <title>Re: SQL Warehouse Configuration Tweaking</title>
      <link>https://community.databricks.com/t5/data-engineering/sql-warehouse-configuration-tweaking/m-p/11148#M6176</link>
      <description>&lt;P&gt;Thanks for the link, my Google-Fu was weak and I hadn't found anything that specifically referenced which hardware was being used under the hood... I mostly worked it via trial and error &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 20 Jan 2023 02:52:13 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/sql-warehouse-configuration-tweaking/m-p/11148#M6176</guid>
      <dc:creator>najmead</dc:creator>
      <dc:date>2023-01-20T02:52:13Z</dc:date>
    </item>
  </channel>
</rss>

