<?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: Naming conventions for delta sharing in Data Governance</title>
    <link>https://community.databricks.com/t5/data-governance/naming-conventions-for-delta-sharing/m-p/101580#M2299</link>
    <description>&lt;P&gt;For platform-to-platform environments, I nest all shared tables under a specially named Schema with a prefix of DS-.&amp;nbsp; For example, my schema name could be &lt;STRONG&gt;ds-mfgschema&lt;/STRONG&gt;. This is a 'flag' that any tables nested under this schema are being delta shared with others. Of course, you could do this same naming convention at the Catalog level as well (or even at the table level). But I find doing this convention at the schema level simple and effective.&lt;/P&gt;</description>
    <pubDate>Tue, 10 Dec 2024 10:50:17 GMT</pubDate>
    <dc:creator>mark_ott</dc:creator>
    <dc:date>2024-12-10T10:50:17Z</dc:date>
    <item>
      <title>Naming conventions for delta sharing</title>
      <link>https://community.databricks.com/t5/data-governance/naming-conventions-for-delta-sharing/m-p/99255#M2265</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;A question for those using Delta Sharing, how are you defining naming conventions for Shares and Recipient names? What best practices or standards are you following? Thanks, Fatima&lt;/P&gt;</description>
      <pubDate>Mon, 18 Nov 2024 22:31:23 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-governance/naming-conventions-for-delta-sharing/m-p/99255#M2265</guid>
      <dc:creator>F_Goudarzi</dc:creator>
      <dc:date>2024-11-18T22:31:23Z</dc:date>
    </item>
    <item>
      <title>Re: Naming conventions for delta sharing</title>
      <link>https://community.databricks.com/t5/data-governance/naming-conventions-for-delta-sharing/m-p/101580#M2299</link>
      <description>&lt;P&gt;For platform-to-platform environments, I nest all shared tables under a specially named Schema with a prefix of DS-.&amp;nbsp; For example, my schema name could be &lt;STRONG&gt;ds-mfgschema&lt;/STRONG&gt;. This is a 'flag' that any tables nested under this schema are being delta shared with others. Of course, you could do this same naming convention at the Catalog level as well (or even at the table level). But I find doing this convention at the schema level simple and effective.&lt;/P&gt;</description>
      <pubDate>Tue, 10 Dec 2024 10:50:17 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-governance/naming-conventions-for-delta-sharing/m-p/101580#M2299</guid>
      <dc:creator>mark_ott</dc:creator>
      <dc:date>2024-12-10T10:50:17Z</dc:date>
    </item>
    <item>
      <title>Re: Naming conventions for delta sharing</title>
      <link>https://community.databricks.com/t5/data-governance/naming-conventions-for-delta-sharing/m-p/101627#M2304</link>
      <description>&lt;P&gt;Thanks Mark. I did not get you completely. Is the "&lt;STRONG&gt;ds-mfgschema&lt;/STRONG&gt;" share name or schema name?&lt;/P&gt;</description>
      <pubDate>Tue, 10 Dec 2024 15:21:25 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-governance/naming-conventions-for-delta-sharing/m-p/101627#M2304</guid>
      <dc:creator>F_Goudarzi</dc:creator>
      <dc:date>2024-12-10T15:21:25Z</dc:date>
    </item>
  </channel>
</rss>

