<?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>article Tracing data lineage for SnowSQL in Talend Data Catalog in Member Articles</title>
    <link>https://community.qlik.com/t5/Member-Articles/Tracing-data-lineage-for-SnowSQL-in-Talend-Data-Catalog/ta-p/2413603</link>
    <description>&lt;P&gt;This article shows you how to configure two Talend Data Catalog bridges to harvest metadata from Snowflake and trace data lineage. It covers the &lt;A href="https://help.qlik.com/talend/en-US/talend-data-catalog/8.1/Subsystems/Bridges/Content/MIRJdbcSnowflakeImport.htm" target="_blank" rel="noopener"&gt;Snowflake Database (via JDBC)&lt;/A&gt; and &lt;A href="https://help.qlik.com/talend/en-US/talend-data-catalog/8.1/Subsystems/Bridges/Content/MIRSqlScriptSnowflakeImport.htm" target="_blank" rel="noopener"&gt;Snowflake Database SQL DML (DI/ETL) Script (SnowSQL)&lt;/A&gt; Talend Data Catalog bridges.&lt;/P&gt;
&lt;H3&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Configuring the Snowflake database bridge import setup&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;P&gt;Configure the import setup parameters for harvesting metadata from a Snowflake database in Talend Data Catalog:&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;
&lt;P&gt;Define the following parameters on the &lt;STRONG&gt;Import Setup&lt;/STRONG&gt; tab: &lt;STRONG&gt;Host&lt;/STRONG&gt;, &lt;STRONG&gt;Warehouse&lt;/STRONG&gt;, &lt;STRONG&gt;Databases&lt;/STRONG&gt;, and the &lt;STRONG&gt;User&lt;/STRONG&gt; and &lt;STRONG&gt;Password&lt;/STRONG&gt; for authentication.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;&lt;SPAN&gt;Select the schemas to be harvested in the Schema field. This example uses the&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG style="font-family: inherit;"&gt;TDC_TEST&lt;/STRONG&gt;&lt;SPAN&gt;, &lt;/SPAN&gt;&lt;STRONG style="font-family: inherit;"&gt;TESTSCHEMA1&lt;/STRONG&gt;&lt;SPAN&gt;, and &lt;/SPAN&gt;&lt;STRONG style="font-family: inherit;"&gt;TESTSCHEMA2&amp;nbsp;&lt;/STRONG&gt;&lt;SPAN&gt;schemas.&lt;/SPAN&gt;&lt;/P&gt;
&lt;DIV id="tinyMceEditorShicong_Hong_2" class="mceNonEditable lia-copypaste-placeholder"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Shicong_Hong_3-1728870343274.png" style="width: 999px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/172865iD324C48EAA355D14/image-size/large?v=v2&amp;amp;px=999" role="button" title="Shicong_Hong_3-1728870343274.png" alt="Shicong_Hong_3-1728870343274.png" /&gt;&lt;/span&gt;&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;Go to the &lt;STRONG&gt;Overview &lt;/STRONG&gt;tab to view an overview of the objects harvested from the Snowflake database.&lt;/P&gt;
&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Shicong_Hong_4-1728870397512.png" style="width: 999px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/172866iA45533491B8B95FD/image-size/large?v=v2&amp;amp;px=999" role="button" title="Shicong_Hong_4-1728870397512.png" alt="Shicong_Hong_4-1728870397512.png" /&gt;&lt;/span&gt;&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;&lt;STRONG&gt;&lt;FONT color="#339966"&gt;Configuring the SnowSQL bridge import setup&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/H3&gt;
&lt;P&gt;This example SnowSQL script contains a create view Data Manipulation Language (DML) statement:&lt;/P&gt;
&lt;PRE class="ckeditor_codeblock"&gt;create view IF NOT EXISTS testschema2.v_employees (
employee_id,
employee_name
) as select
rvalue:employee_id::number,
rvalue:employee_name::string
from testschema1.employees;
&lt;/PRE&gt;
&lt;P&gt;You will harvest metadata from this example SnowSQL script in the steps below.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;To configure the parameters for the Snowflake Database SQL DML (DI/ETL) Script (SnowSQL) bridge in Talend Data Catalog:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;
&lt;P&gt;Define the &lt;STRONG&gt;Directory&lt;/STRONG&gt; where the SnowSQL file is located on the &lt;STRONG&gt;Import Setup&lt;/STRONG&gt; tab.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;Add any necessary &lt;STRONG&gt;Include&lt;/STRONG&gt; and &lt;STRONG&gt;Exclude &lt;/STRONG&gt;filters to select the files to be harvested.&lt;/P&gt;
&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Shicong_Hong_5-1728870568234.png" style="width: 999px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/172867i7E35C49BBE04BE43/image-size/large?v=v2&amp;amp;px=999" role="button" title="Shicong_Hong_5-1728870568234.png" alt="Shicong_Hong_5-1728870568234.png" /&gt;&lt;/span&gt;&amp;nbsp;&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;Go to the &lt;STRONG&gt;Overview&lt;/STRONG&gt; tab to view the imported SnowSQL script.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Shicong_Hong_6-1728870606064.png" style="width: 999px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/172868i47AF840DEFC3BAEC/image-size/large?v=v2&amp;amp;px=999" role="button" title="Shicong_Hong_6-1728870606064.png" alt="Shicong_Hong_6-1728870606064.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;View the connection defined for the SnowSQL model in the &lt;STRONG&gt;Configuration Manager.&lt;/STRONG&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Shicong_Hong_0-1728871701746.png" style="width: 999px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/172877iA3BDADE83F0577DD/image-size/large?v=v2&amp;amp;px=999" role="button" title="Shicong_Hong_0-1728871701746.png" alt="Shicong_Hong_0-1728871701746.png" /&gt;&lt;/span&gt;&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Tracing data lineage for a field/column in the SnowSQL script&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;OL&gt;
&lt;LI&gt;
&lt;P&gt;Notice that after harvesting metadata (database objects and SnowSQL) using both bridges and building the configuration, the Architecture Diagram displays a bi-directional arrow, because the same Snowflake database model is the source and destination connection to the database.&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="2024-10-14_10-00-37.png" style="width: 931px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/172873iC78E94BAB51E8A1F/image-size/large?v=v2&amp;amp;px=999" role="button" title="2024-10-14_10-00-37.png" alt="2024-10-14_10-00-37.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;Go to the &lt;STRONG&gt;Data Flow&lt;/STRONG&gt; tab to view the data flow diagram for the SnowSQL script. Referring to the SnowSQL script, Talend Data Catalog creates a view on one schema (&lt;STRONG&gt;TESTSCHEMA2&lt;/STRONG&gt;) with a select statement on another schema (&lt;STRONG&gt;TESTSCHEMA1&lt;/STRONG&gt;).&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="2024-10-14_10-01-28.png" style="width: 999px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/172874i36FF8EA2EE13541F/image-size/large?v=v2&amp;amp;px=999" role="button" title="2024-10-14_10-01-28.png" alt="2024-10-14_10-01-28.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;You can also view the data flow diagram for the database object (schema level), which displays the three schemas.&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="2024-10-14_10-03-12.png" style="width: 999px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/172875i82532DB4CA07A488/image-size/large?v=v2&amp;amp;px=999" role="button" title="2024-10-14_10-03-12.png" alt="2024-10-14_10-03-12.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;Finally, you can display the data lineage for a column (&lt;STRONG&gt;EMPLOYEE_NAME&lt;/STRONG&gt;).&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="2024-10-14_10-04-11.png" style="width: 999px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/172876i14CEAAFD7FE70F27/image-size/large?v=v2&amp;amp;px=999" role="button" title="2024-10-14_10-04-11.png" alt="2024-10-14_10-04-11.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H4&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Environment&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H4&gt;
&lt;UL&gt;
&lt;LI&gt;Talend Data Integration 8.0.1&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 14 Oct 2024 03:18:59 GMT</pubDate>
    <dc:creator>Donna_Carr</dc:creator>
    <dc:date>2024-10-14T03:18:59Z</dc:date>
    <item>
      <title>Tracing data lineage for SnowSQL in Talend Data Catalog</title>
      <link>https://community.qlik.com/t5/Member-Articles/Tracing-data-lineage-for-SnowSQL-in-Talend-Data-Catalog/ta-p/2413603</link>
      <description>&lt;P&gt;This article provides a way to trace data lineage for a SnowSQL script. The scenario uses a Snowflake database table and Data Manipulation Language (DML) within a SnowSQL script.&lt;/P&gt;</description>
      <pubDate>Mon, 14 Oct 2024 03:18:59 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Member-Articles/Tracing-data-lineage-for-SnowSQL-in-Talend-Data-Catalog/ta-p/2413603</guid>
      <dc:creator>Donna_Carr</dc:creator>
      <dc:date>2024-10-14T03:18:59Z</dc:date>
    </item>
  </channel>
</rss>

