<?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: Shouldn't the global statement_timeout parameter prevail over the session parameter? in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/shouldn-t-the-global-statement-timeout-parameter-prevail-over/m-p/103619#M41520</link>
    <description>&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="srtiemann1_0-1735586550774.png" style="width: 400px;"&gt;&lt;img src="https://community.databricks.com/t5/image/serverpage/image-id/13779i15E1A2C83058D458/image-size/medium?v=v2&amp;amp;px=400" role="button" title="srtiemann1_0-1735586550774.png" alt="srtiemann1_0-1735586550774.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 30 Dec 2024 19:24:48 GMT</pubDate>
    <dc:creator>srtiemann1</dc:creator>
    <dc:date>2024-12-30T19:24:48Z</dc:date>
    <item>
      <title>Shouldn't the global statement_timeout parameter prevail over the session parameter?</title>
      <link>https://community.databricks.com/t5/data-engineering/shouldn-t-the-global-statement-timeout-parameter-prevail-over/m-p/102500#M41146</link>
      <description>&lt;P&gt;How can I block the use of statement_timeout at the session level in Databricks? I want the global parameter to be enforced even if a SET statement_timeout has been executed in Databricks notebooks."&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 18 Dec 2024 14:30:52 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/shouldn-t-the-global-statement-timeout-parameter-prevail-over/m-p/102500#M41146</guid>
      <dc:creator>srtiemann</dc:creator>
      <dc:date>2024-12-18T14:30:52Z</dc:date>
    </item>
    <item>
      <title>Re: Shouldn't the global statement_timeout parameter prevail over the session parameter?</title>
      <link>https://community.databricks.com/t5/data-engineering/shouldn-t-the-global-statement-timeout-parameter-prevail-over/m-p/102501#M41147</link>
      <description>&lt;P&gt;To set a workspace-level timeout, go to the workspace admin settings, click&amp;nbsp;&lt;STRONG&gt;Compute&lt;/STRONG&gt;, then click&amp;nbsp;&lt;STRONG&gt;Manage&lt;/STRONG&gt;&amp;nbsp;next to&amp;nbsp;&lt;STRONG&gt;SQL warehouses&lt;/STRONG&gt;. In the&amp;nbsp;&lt;STRONG&gt;SQL Configuration Parameters&lt;/STRONG&gt;&amp;nbsp;setting, add a configuration parameter where the timeout value is in seconds.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://docs.databricks.com/ja/sql/language-manual/parameters/statement_timeout.html" target="_blank"&gt;https://docs.databricks.com/ja/sql/language-manual/parameters/statement_timeout.html&lt;/A&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 18 Dec 2024 14:47:28 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/shouldn-t-the-global-statement-timeout-parameter-prevail-over/m-p/102501#M41147</guid>
      <dc:creator>Walter_C</dc:creator>
      <dc:date>2024-12-18T14:47:28Z</dc:date>
    </item>
    <item>
      <title>Re: Shouldn't the global statement_timeout parameter prevail over the session parameter?</title>
      <link>https://community.databricks.com/t5/data-engineering/shouldn-t-the-global-statement-timeout-parameter-prevail-over/m-p/102576#M41164</link>
      <description>&lt;P&gt;I did this, but when a user uses the set statement_timeout command in their own Databricks notebook, the query exceeds the time determined by the global parameter&lt;/P&gt;</description>
      <pubDate>Wed, 18 Dec 2024 20:26:42 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/shouldn-t-the-global-statement-timeout-parameter-prevail-over/m-p/102576#M41164</guid>
      <dc:creator>srtiemann</dc:creator>
      <dc:date>2024-12-18T20:26:42Z</dc:date>
    </item>
    <item>
      <title>Re: Shouldn't the global statement_timeout parameter prevail over the session parameter?</title>
      <link>https://community.databricks.com/t5/data-engineering/shouldn-t-the-global-statement-timeout-parameter-prevail-over/m-p/102577#M41165</link>
      <description>&lt;P&gt;Is the notebook pointing to an SQL warehouse or it is pointing to an all purpose cluster or serverless compute?&lt;/P&gt;</description>
      <pubDate>Wed, 18 Dec 2024 20:30:09 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/shouldn-t-the-global-statement-timeout-parameter-prevail-over/m-p/102577#M41165</guid>
      <dc:creator>Walter_C</dc:creator>
      <dc:date>2024-12-18T20:30:09Z</dc:date>
    </item>
    <item>
      <title>Re: Shouldn't the global statement_timeout parameter prevail over the session parameter?</title>
      <link>https://community.databricks.com/t5/data-engineering/shouldn-t-the-global-statement-timeout-parameter-prevail-over/m-p/102579#M41166</link>
      <description>&lt;P&gt;&lt;SPAN&gt;serverless&amp;nbsp;compute SQL&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 18 Dec 2024 20:33:34 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/shouldn-t-the-global-statement-timeout-parameter-prevail-over/m-p/102579#M41166</guid>
      <dc:creator>srtiemann</dc:creator>
      <dc:date>2024-12-18T20:33:34Z</dc:date>
    </item>
    <item>
      <title>Re: Shouldn't the global statement_timeout parameter prevail over the session parameter?</title>
      <link>https://community.databricks.com/t5/data-engineering/shouldn-t-the-global-statement-timeout-parameter-prevail-over/m-p/102584#M41169</link>
      <description>&lt;P&gt;To revalidate this, are you using Serverless SQL Warehouse or Serverless Compute which are different? Can you share an screenshot of the compute being used to make sure we are aligned?&lt;/P&gt;</description>
      <pubDate>Wed, 18 Dec 2024 21:08:15 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/shouldn-t-the-global-statement-timeout-parameter-prevail-over/m-p/102584#M41169</guid>
      <dc:creator>Walter_C</dc:creator>
      <dc:date>2024-12-18T21:08:15Z</dc:date>
    </item>
    <item>
      <title>Re: Shouldn't the global statement_timeout parameter prevail over the session parameter?</title>
      <link>https://community.databricks.com/t5/data-engineering/shouldn-t-the-global-statement-timeout-parameter-prevail-over/m-p/103619#M41520</link>
      <description>&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="srtiemann1_0-1735586550774.png" style="width: 400px;"&gt;&lt;img src="https://community.databricks.com/t5/image/serverpage/image-id/13779i15E1A2C83058D458/image-size/medium?v=v2&amp;amp;px=400" role="button" title="srtiemann1_0-1735586550774.png" alt="srtiemann1_0-1735586550774.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 30 Dec 2024 19:24:48 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/shouldn-t-the-global-statement-timeout-parameter-prevail-over/m-p/103619#M41520</guid>
      <dc:creator>srtiemann1</dc:creator>
      <dc:date>2024-12-30T19:24:48Z</dc:date>
    </item>
    <item>
      <title>Re: Shouldn't the global statement_timeout parameter prevail over the session parameter?</title>
      <link>https://community.databricks.com/t5/data-engineering/shouldn-t-the-global-statement-timeout-parameter-prevail-over/m-p/103627#M41523</link>
      <description>&lt;P&gt;Yes, this global config only applies to Serverless SQL Warehouses, but wont apply if you use serverless compute for notebooks&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 30 Dec 2024 21:24:17 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/shouldn-t-the-global-statement-timeout-parameter-prevail-over/m-p/103627#M41523</guid>
      <dc:creator>Walter_C</dc:creator>
      <dc:date>2024-12-30T21:24:17Z</dc:date>
    </item>
  </channel>
</rss>

