<?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: temp tables in Databricks in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/temp-tables-in-databricks/m-p/45115#M27795</link>
    <description>&lt;P&gt;Just to add a bit more from experience&lt;/P&gt;&lt;P&gt;If you are doing to use the temp tables too many times, then using temp views is going to slow down your cluster . It is due to lazy evaluation unless you persist that view (dataframe cache or globaltempview).&lt;/P&gt;&lt;P&gt;Every time your temp view is called, it will execute the view definition/code. This also depends upon your cluster capacity, how complex the view definition is, how much data the temp view has.&lt;/P&gt;&lt;P&gt;Please correct me if I am wrong.&lt;/P&gt;</description>
    <pubDate>Sat, 16 Sep 2023 15:25:43 GMT</pubDate>
    <dc:creator>berserkersap</dc:creator>
    <dc:date>2023-09-16T15:25:43Z</dc:date>
    <item>
      <title>temp tables in Databricks</title>
      <link>https://community.databricks.com/t5/data-engineering/temp-tables-in-databricks/m-p/44012#M27590</link>
      <description>&lt;P&gt;Hey Team,&lt;/P&gt;&lt;P&gt;We are in a migration phase from SQL server to Databricks.&lt;/P&gt;&lt;P&gt;In our sql server databricks, lot of times, #temp tables created and dropped like typical Datawarehousing sql.&lt;/P&gt;&lt;P&gt;In Databricks, we can do 2 things. I want to check which one is best approach and why?&lt;/P&gt;&lt;P&gt;1) create temp views in databricks and make use of views later in the query&lt;/P&gt;&lt;P&gt;2) create delta table with temp(prefix) and make use of temp table and at the end drop temp table.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;I am looking forward for your response.&lt;/P&gt;</description>
      <pubDate>Thu, 07 Sep 2023 15:30:38 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/temp-tables-in-databricks/m-p/44012#M27590</guid>
      <dc:creator>AMadan</dc:creator>
      <dc:date>2023-09-07T15:30:38Z</dc:date>
    </item>
    <item>
      <title>Re: temp tables in Databricks</title>
      <link>https://community.databricks.com/t5/data-engineering/temp-tables-in-databricks/m-p/45115#M27795</link>
      <description>&lt;P&gt;Just to add a bit more from experience&lt;/P&gt;&lt;P&gt;If you are doing to use the temp tables too many times, then using temp views is going to slow down your cluster . It is due to lazy evaluation unless you persist that view (dataframe cache or globaltempview).&lt;/P&gt;&lt;P&gt;Every time your temp view is called, it will execute the view definition/code. This also depends upon your cluster capacity, how complex the view definition is, how much data the temp view has.&lt;/P&gt;&lt;P&gt;Please correct me if I am wrong.&lt;/P&gt;</description>
      <pubDate>Sat, 16 Sep 2023 15:25:43 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/temp-tables-in-databricks/m-p/45115#M27795</guid>
      <dc:creator>berserkersap</dc:creator>
      <dc:date>2023-09-16T15:25:43Z</dc:date>
    </item>
  </channel>
</rss>

