<?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: Creating a test schema - what is the best practice? in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/creating-a-test-schema-what-is-the-best-practice/m-p/38308#M26603</link>
    <description>&lt;P&gt;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/31813"&gt;@Asterol&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you would like to have the same data for your Dev/testing environment, I would recommend using Deep Clone. Deep clone copies the metadata and creates an independent copy of the table data.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Shallow clone only copies the metadata and will have a pointer to your production data. Shallow clone only helps for short-lived use cases.&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you end goal is to create a Dev/testing/production environment, Deep Clone is the way forward. This would help you in using and maintaining them independently.&lt;/P&gt;</description>
    <pubDate>Tue, 25 Jul 2023 05:17:39 GMT</pubDate>
    <dc:creator>Tharun-Kumar</dc:creator>
    <dc:date>2023-07-25T05:17:39Z</dc:date>
    <item>
      <title>Creating a test schema - what is the best practice?</title>
      <link>https://community.databricks.com/t5/data-engineering/creating-a-test-schema-what-is-the-best-practice/m-p/38250#M26589</link>
      <description>&lt;UL&gt;&lt;LI&gt;Hey,&amp;nbsp;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;I've created a schema with few tables with historical data (prod), now I would like to have a Dev/testing environment with exactly the same data.&lt;/P&gt;&lt;P&gt;What do you recommend? CTAS? Shallow clone? Deep clone? I wonder if shallow clone would be sufficient, what is your experience?&lt;/P&gt;</description>
      <pubDate>Mon, 24 Jul 2023 07:00:45 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/creating-a-test-schema-what-is-the-best-practice/m-p/38250#M26589</guid>
      <dc:creator>Asterol</dc:creator>
      <dc:date>2023-07-24T07:00:45Z</dc:date>
    </item>
    <item>
      <title>Re: Creating a test schema - what is the best practice?</title>
      <link>https://community.databricks.com/t5/data-engineering/creating-a-test-schema-what-is-the-best-practice/m-p/38308#M26603</link>
      <description>&lt;P&gt;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/31813"&gt;@Asterol&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you would like to have the same data for your Dev/testing environment, I would recommend using Deep Clone. Deep clone copies the metadata and creates an independent copy of the table data.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Shallow clone only copies the metadata and will have a pointer to your production data. Shallow clone only helps for short-lived use cases.&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you end goal is to create a Dev/testing/production environment, Deep Clone is the way forward. This would help you in using and maintaining them independently.&lt;/P&gt;</description>
      <pubDate>Tue, 25 Jul 2023 05:17:39 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/creating-a-test-schema-what-is-the-best-practice/m-p/38308#M26603</guid>
      <dc:creator>Tharun-Kumar</dc:creator>
      <dc:date>2023-07-25T05:17:39Z</dc:date>
    </item>
  </channel>
</rss>

