<?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 Azure Databricks SQL Warehouse connection issue in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/azure-databricks-sql-warehouse-connection-issue/m-p/31790#M23160</link>
    <description>&lt;P&gt;When trying to start SQL Warehouse from my Azure pay-as-you-go subscription, I'm getting error about not enough vCPUs provisioned. Documentation says to increase quota at Azure portal - but it requires knowing type of vCPUs to provision. What type of CPUs should be provisioned? Is it EDSv4 family, or spot instances, or something else? What is the best way to see what clusters each t-shirt size of SQL Warehouse is using? Thank you.&lt;/P&gt;</description>
    <pubDate>Wed, 14 Sep 2022 02:29:42 GMT</pubDate>
    <dc:creator>Yuliya</dc:creator>
    <dc:date>2022-09-14T02:29:42Z</dc:date>
    <item>
      <title>Azure Databricks SQL Warehouse connection issue</title>
      <link>https://community.databricks.com/t5/data-engineering/azure-databricks-sql-warehouse-connection-issue/m-p/31790#M23160</link>
      <description>&lt;P&gt;When trying to start SQL Warehouse from my Azure pay-as-you-go subscription, I'm getting error about not enough vCPUs provisioned. Documentation says to increase quota at Azure portal - but it requires knowing type of vCPUs to provision. What type of CPUs should be provisioned? Is it EDSv4 family, or spot instances, or something else? What is the best way to see what clusters each t-shirt size of SQL Warehouse is using? Thank you.&lt;/P&gt;</description>
      <pubDate>Wed, 14 Sep 2022 02:29:42 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/azure-databricks-sql-warehouse-connection-issue/m-p/31790#M23160</guid>
      <dc:creator>Yuliya</dc:creator>
      <dc:date>2022-09-14T02:29:42Z</dc:date>
    </item>
    <item>
      <title>Re: Azure Databricks SQL Warehouse connection issue</title>
      <link>https://community.databricks.com/t5/data-engineering/azure-databricks-sql-warehouse-connection-issue/m-p/31791#M23161</link>
      <description>&lt;P&gt;it is documented here: &lt;A href="https://docs.microsoft.com/en-us/azure/databricks/sql/admin/sql-endpoints#sql-endpoints-name-changed-to-sql-warehouses" target="test_blank"&gt;https://docs.microsoft.com/en-us/azure/databricks/sql/admin/sql-endpoints#sql-endpoints-name-changed-to-sql-warehouses&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With 2X-Small size you allocate 1x Standard_E8ds_v4 for driver and 1x Standard_E8ds_v4 for worker. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When configuring a SQL warehouse you can chose between reliability optimized (=full price VMs) and cost optimized (=spot VMs for workers).&lt;/P&gt;</description>
      <pubDate>Thu, 15 Sep 2022 19:20:19 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/azure-databricks-sql-warehouse-connection-issue/m-p/31791#M23161</guid>
      <dc:creator>Rostislaw</dc:creator>
      <dc:date>2022-09-15T19:20:19Z</dc:date>
    </item>
    <item>
      <title>Re: Azure Databricks SQL Warehouse connection issue</title>
      <link>https://community.databricks.com/t5/data-engineering/azure-databricks-sql-warehouse-connection-issue/m-p/31792#M23162</link>
      <description>&lt;P&gt;Hi @Yuliya Quintela​,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just a friendly follow-up. Did Rostislaw's response help you to resolve your question? if it did, please mark it as best. Otherwise, please let us know if you still need help.&lt;/P&gt;</description>
      <pubDate>Tue, 27 Sep 2022 15:40:43 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/azure-databricks-sql-warehouse-connection-issue/m-p/31792#M23162</guid>
      <dc:creator>jose_gonzalez</dc:creator>
      <dc:date>2022-09-27T15:40:43Z</dc:date>
    </item>
  </channel>
</rss>

