<?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: Managed Table in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/managed-table/m-p/96865#M39356</link>
    <description>&lt;P&gt;&lt;FONT&gt;&lt;FONT&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/108321"&gt;@Mani2105&lt;/a&gt;,&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;if i create a table in the sales catalog without&amp;nbsp; specifiying any external location, will the tables created be managed and will go to the Sales storage account&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT&gt;&lt;FONT&gt;&lt;span class="lia-unicode-emoji" title=":backhand_index_pointing_right:"&gt;👉&lt;/span&gt; Yes, if you create a table in the sales catalog without specifying any external location, this table will be automatically managed and the data will be stored in the default storage location configured for the sales catalog.&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;and in the event of deleting the table ,will it delete the files associated as welland auto optimize?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;span class="lia-unicode-emoji" title=":backhand_index_pointing_right:"&gt;👉&lt;/span&gt;&amp;nbsp;&lt;/STRONG&gt;Yes, in the case of managed tables within Unity Catalog in Databricks, deleting the table will also delete the associated files stored in the catalog’s storage location&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Delta Lake’s auto-optimization features&lt;/STRONG&gt; (like autoCompact and optimizeWrite) apply to managed tables. If you’ve enabled these settings, they will continuously optimize the storage layout, such as compacting small files or applying Z-ordering, to improve query performance and storage efficiency.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;You can enable auto-optimization for the entire workspace, catalog, or individual tables using configuration settings:&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="python"&gt;# Enabling auto-optimization
spark.conf.set("spark.databricks.delta.autoCompact.enabled", "true")
spark.conf.set("spark.databricks.delta.optimizeWrite.enabled", "true")&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;What will my metastore USDATA have information about the sales catalog , if the sales catalog had a seperate storage location , its the metadata about the catalog goes to metastore?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":backhand_index_pointing_right:"&gt;👉&lt;/span&gt; The USDATA metastore stores metadata for all catalogs in your workspace, including the Sales catalog.&amp;nbsp;Although Sales has a separate storage location, &lt;STRONG&gt;only metadata about Sales (such as its tables, schemas, and storage path) is stored in the USDATA metastore&lt;/STRONG&gt;—the actual data files reside in the storage location designated for Sales.&lt;/P&gt;&lt;P&gt;The metastore (USDATA) holds &lt;STRONG&gt;metadata about all catalogs, schemas, and tables&lt;/STRONG&gt; within your Databricks workspace, including:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Information about each catalog (e.g., Sales).&lt;/LI&gt;&lt;LI&gt;Schemas (databases) within each catalog.&lt;/LI&gt;&lt;LI&gt;Tables and views, including details such as columns, data types, and table properties.&lt;/LI&gt;&lt;LI&gt;Access control configurations, permissions, and security settings.&lt;/LI&gt;&lt;/UL&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;P&gt;&lt;STRONG&gt;Let me know if you’d like more details on any part of this process!&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Regards!&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 30 Oct 2024 17:20:12 GMT</pubDate>
    <dc:creator>agallard</dc:creator>
    <dc:date>2024-10-30T17:20:12Z</dc:date>
    <item>
      <title>Managed Table</title>
      <link>https://community.databricks.com/t5/data-engineering/managed-table/m-p/96572#M39296</link>
      <description>&lt;P&gt;Hi Experts,&lt;/P&gt;&lt;P&gt;I have a workspace created and associated a metastore with it, the metastore points to a storage location USDATA and then I create two catalogs in the workspace and one is using default meta store as the external storage location and other catalog is sales and i created a external sales storage location and provided security access.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Mani2105_0-1730143852722.png" style="width: 400px;"&gt;&lt;img src="https://community.databricks.com/t5/image/serverpage/image-id/12345iEEFB3A0B1E571397/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Mani2105_0-1730143852722.png" alt="Mani2105_0-1730143852722.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Abive screen shot&amp;nbsp; says storage for managed tables on external locations, so now my question is if i create a table in the sales catalog without&amp;nbsp; specifiying any external location, will the tables created be managed and will go to the Sales storage account and in the event of deleting the table ,will it delete the files associated as welland auto optimize? What will my metastore&amp;nbsp;USDATA&amp;nbsp; have information about the sales catalog , if the sales catalog had a seperate storage location , its the metadata about the catalog goes to metastore?&lt;/P&gt;</description>
      <pubDate>Mon, 28 Oct 2024 19:35:16 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/managed-table/m-p/96572#M39296</guid>
      <dc:creator>Mani2105</dc:creator>
      <dc:date>2024-10-28T19:35:16Z</dc:date>
    </item>
    <item>
      <title>Re: Managed Table</title>
      <link>https://community.databricks.com/t5/data-engineering/managed-table/m-p/96865#M39356</link>
      <description>&lt;P&gt;&lt;FONT&gt;&lt;FONT&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/108321"&gt;@Mani2105&lt;/a&gt;,&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;if i create a table in the sales catalog without&amp;nbsp; specifiying any external location, will the tables created be managed and will go to the Sales storage account&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT&gt;&lt;FONT&gt;&lt;span class="lia-unicode-emoji" title=":backhand_index_pointing_right:"&gt;👉&lt;/span&gt; Yes, if you create a table in the sales catalog without specifying any external location, this table will be automatically managed and the data will be stored in the default storage location configured for the sales catalog.&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;and in the event of deleting the table ,will it delete the files associated as welland auto optimize?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;span class="lia-unicode-emoji" title=":backhand_index_pointing_right:"&gt;👉&lt;/span&gt;&amp;nbsp;&lt;/STRONG&gt;Yes, in the case of managed tables within Unity Catalog in Databricks, deleting the table will also delete the associated files stored in the catalog’s storage location&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Delta Lake’s auto-optimization features&lt;/STRONG&gt; (like autoCompact and optimizeWrite) apply to managed tables. If you’ve enabled these settings, they will continuously optimize the storage layout, such as compacting small files or applying Z-ordering, to improve query performance and storage efficiency.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;You can enable auto-optimization for the entire workspace, catalog, or individual tables using configuration settings:&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="python"&gt;# Enabling auto-optimization
spark.conf.set("spark.databricks.delta.autoCompact.enabled", "true")
spark.conf.set("spark.databricks.delta.optimizeWrite.enabled", "true")&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;What will my metastore USDATA have information about the sales catalog , if the sales catalog had a seperate storage location , its the metadata about the catalog goes to metastore?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":backhand_index_pointing_right:"&gt;👉&lt;/span&gt; The USDATA metastore stores metadata for all catalogs in your workspace, including the Sales catalog.&amp;nbsp;Although Sales has a separate storage location, &lt;STRONG&gt;only metadata about Sales (such as its tables, schemas, and storage path) is stored in the USDATA metastore&lt;/STRONG&gt;—the actual data files reside in the storage location designated for Sales.&lt;/P&gt;&lt;P&gt;The metastore (USDATA) holds &lt;STRONG&gt;metadata about all catalogs, schemas, and tables&lt;/STRONG&gt; within your Databricks workspace, including:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Information about each catalog (e.g., Sales).&lt;/LI&gt;&lt;LI&gt;Schemas (databases) within each catalog.&lt;/LI&gt;&lt;LI&gt;Tables and views, including details such as columns, data types, and table properties.&lt;/LI&gt;&lt;LI&gt;Access control configurations, permissions, and security settings.&lt;/LI&gt;&lt;/UL&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;P&gt;&lt;STRONG&gt;Let me know if you’d like more details on any part of this process!&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Regards!&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 30 Oct 2024 17:20:12 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/managed-table/m-p/96865#M39356</guid>
      <dc:creator>agallard</dc:creator>
      <dc:date>2024-10-30T17:20:12Z</dc:date>
    </item>
  </channel>
</rss>

