<?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 MV Table in a business schema in Data &amp; Schema Discussions</title>
    <link>https://community.incorta.com/t5/data-schema-discussions/mv-table-in-a-business-schema/m-p/4475#M350</link>
    <description>&lt;P&gt;Dear all,&lt;/P&gt;&lt;P&gt;is it possible to create a MV from two tables in a physical schema and use this MV in the business schema ?&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 14 Jun 2023 20:38:28 GMT</pubDate>
    <dc:creator>lgualco</dc:creator>
    <dc:date>2023-06-14T20:38:28Z</dc:date>
    <item>
      <title>MV Table in a business schema</title>
      <link>https://community.incorta.com/t5/data-schema-discussions/mv-table-in-a-business-schema/m-p/4475#M350</link>
      <description>&lt;P&gt;Dear all,&lt;/P&gt;&lt;P&gt;is it possible to create a MV from two tables in a physical schema and use this MV in the business schema ?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 14 Jun 2023 20:38:28 GMT</pubDate>
      <guid>https://community.incorta.com/t5/data-schema-discussions/mv-table-in-a-business-schema/m-p/4475#M350</guid>
      <dc:creator>lgualco</dc:creator>
      <dc:date>2023-06-14T20:38:28Z</dc:date>
    </item>
    <item>
      <title>Re: MV Table in a business schema</title>
      <link>https://community.incorta.com/t5/data-schema-discussions/mv-table-in-a-business-schema/m-p/4476#M351</link>
      <description>&lt;P&gt;Is the MV you are referring to joining two tables? Yes, once you've created the MV and loaded it, it will be available to be built into a view in the business schema.&lt;/P&gt;</description>
      <pubDate>Thu, 15 Jun 2023 18:49:58 GMT</pubDate>
      <guid>https://community.incorta.com/t5/data-schema-discussions/mv-table-in-a-business-schema/m-p/4476#M351</guid>
      <dc:creator>JoeM</dc:creator>
      <dc:date>2023-06-15T18:49:58Z</dc:date>
    </item>
    <item>
      <title>Re: MV Table in a business schema</title>
      <link>https://community.incorta.com/t5/data-schema-discussions/mv-table-in-a-business-schema/m-p/4481#M352</link>
      <description>&lt;P&gt;yes, it will be a join between two tables and and I don't know if the best practices is to use the join feature or this way (with MV used in the dashboard) is also fine,.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 16 Jun 2023 12:26:51 GMT</pubDate>
      <guid>https://community.incorta.com/t5/data-schema-discussions/mv-table-in-a-business-schema/m-p/4481#M352</guid>
      <dc:creator>lgualco</dc:creator>
      <dc:date>2023-06-16T12:26:51Z</dc:date>
    </item>
    <item>
      <title>Re: MV Table in a business schema</title>
      <link>https://community.incorta.com/t5/data-schema-discussions/mv-table-in-a-business-schema/m-p/4483#M353</link>
      <description>&lt;P&gt;I'd suggest that best practices don't prohibit using an MV this way, but you should default to letting the two source tables ( and join ) do the work if there's not compelling reason to put together the MV.&amp;nbsp; &amp;nbsp;&lt;/P&gt;&lt;P&gt;That said, there *are* compelling modeling reasons that exist ( cardinality mostly ) and there's no runtime penalty for using an MV v. any other Incorta table so use them if you need them.&lt;/P&gt;</description>
      <pubDate>Fri, 16 Jun 2023 17:11:01 GMT</pubDate>
      <guid>https://community.incorta.com/t5/data-schema-discussions/mv-table-in-a-business-schema/m-p/4483#M353</guid>
      <dc:creator>RADSr</dc:creator>
      <dc:date>2023-06-16T17:11:01Z</dc:date>
    </item>
  </channel>
</rss>

