<?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: DLT Notebook and Pipeline Separation vs Consolidation in Get Started Discussions</title>
    <link>https://community.databricks.com/t5/get-started-discussions/dlt-notebook-and-pipeline-separation-vs-consolidation/m-p/57848#M2281</link>
    <description>&lt;P&gt;This is great! I completely missed the list view before.&lt;/P&gt;</description>
    <pubDate>Thu, 18 Jan 2024 23:54:28 GMT</pubDate>
    <dc:creator>ChristianRRL</dc:creator>
    <dc:date>2024-01-18T23:54:28Z</dc:date>
    <item>
      <title>DLT Notebook and Pipeline Separation vs Consolidation</title>
      <link>https://community.databricks.com/t5/get-started-discussions/dlt-notebook-and-pipeline-separation-vs-consolidation/m-p/57798#M2277</link>
      <description>&lt;P&gt;Super basic question. For DLT pipelines I see there's an option to add multiple "Paths". Is it generally best practice to completely separate `bronze` from `silver` notebooks? Or is it more recommended to bundle both raw `bronze` and clean `silver` data into notebooks together and separate notebooks by something else?&lt;/P&gt;&lt;P&gt;Similarly, what is an "appropriate" number of tables to process in a single DLT pipeline? E.g. I'm already processing 20 tables from one source and because they're all bronze I have to squint (or realistically just zoom in on the DLT Graph). These 20 bronze tables would flow into 20 silver tables for this current example, but for separate notebook (+maybe separate DLT pipeline) I could see 100s of bronze tables flowing into a few distinct silver tables.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="ChristianRRL_1-1705597040187.png" style="width: 749px;"&gt;&lt;img src="https://community.databricks.com/t5/image/serverpage/image-id/5864i82DAA7B7D8D53D44/image-dimensions/749x148/is-moderation-mode/true?v=v2" width="749" height="148" role="button" title="ChristianRRL_1-1705597040187.png" alt="ChristianRRL_1-1705597040187.png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 18 Jan 2024 17:00:53 GMT</pubDate>
      <guid>https://community.databricks.com/t5/get-started-discussions/dlt-notebook-and-pipeline-separation-vs-consolidation/m-p/57798#M2277</guid>
      <dc:creator>ChristianRRL</dc:creator>
      <dc:date>2024-01-18T17:00:53Z</dc:date>
    </item>
    <item>
      <title>Re: DLT Notebook and Pipeline Separation vs Consolidation</title>
      <link>https://community.databricks.com/t5/get-started-discussions/dlt-notebook-and-pipeline-separation-vs-consolidation/m-p/57825#M2279</link>
      <description>&lt;P&gt;You can run as many tables as you want provided the cluster capacity. Also, if you are processing large no. of tables, using list view in DLT might be a better option as compared to graph view.&lt;/P&gt;</description>
      <pubDate>Thu, 18 Jan 2024 19:27:41 GMT</pubDate>
      <guid>https://community.databricks.com/t5/get-started-discussions/dlt-notebook-and-pipeline-separation-vs-consolidation/m-p/57825#M2279</guid>
      <dc:creator>Lakshay</dc:creator>
      <dc:date>2024-01-18T19:27:41Z</dc:date>
    </item>
    <item>
      <title>Re: DLT Notebook and Pipeline Separation vs Consolidation</title>
      <link>https://community.databricks.com/t5/get-started-discussions/dlt-notebook-and-pipeline-separation-vs-consolidation/m-p/57848#M2281</link>
      <description>&lt;P&gt;This is great! I completely missed the list view before.&lt;/P&gt;</description>
      <pubDate>Thu, 18 Jan 2024 23:54:28 GMT</pubDate>
      <guid>https://community.databricks.com/t5/get-started-discussions/dlt-notebook-and-pipeline-separation-vs-consolidation/m-p/57848#M2281</guid>
      <dc:creator>ChristianRRL</dc:creator>
      <dc:date>2024-01-18T23:54:28Z</dc:date>
    </item>
  </channel>
</rss>

