<?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: updating records using copy job? in Data Engineering</title>
    <link>https://community.fabric.microsoft.com/t5/Data-Engineering/updating-records-using-copy-job/m-p/4746399#M10464</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.fabric.microsoft.com/t5/user/viewprofilepage/user-id/311186"&gt;@Jerome22&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;Unfortunately, in&amp;nbsp;Microsoft Fabric, the&amp;nbsp;Copy Data activity&amp;nbsp;does support an&amp;nbsp;"Upsert"&amp;nbsp;behavior. You can however use&amp;nbsp;workarounds like Dataflows or SQL logic.&lt;BR /&gt;You can refer-&lt;BR /&gt;&lt;A href="https://community.fabric.microsoft.com/t5/Data-Pipeline/upsert-option-missing-in-copy-activity-of-microsoft-fabric-data/m-p/4029524" target="_self"&gt;upsert option missing in copy activity of microsoft fabric data pipeline&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Hope this helps!&lt;BR /&gt;If the response has addressed your query, please&amp;nbsp;accept it as a solution&amp;nbsp;so other members can easily find it.&lt;BR /&gt;Thank You&lt;/P&gt;</description>
    <pubDate>Fri, 27 Jun 2025 10:43:28 GMT</pubDate>
    <dc:creator>v-sdhruv</dc:creator>
    <dc:date>2025-06-27T10:43:28Z</dc:date>
    <item>
      <title>updating records using copy job?</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Engineering/updating-records-using-copy-job/m-p/4745881#M10450</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;when Data copy will support updates and not just adding rows?&lt;/P&gt;&lt;P&gt;I have a lot of tables which can have updated records, so I want to update my destination not just adding new rows.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;thanks.&lt;/P&gt;</description>
      <pubDate>Fri, 27 Jun 2025 02:02:17 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Engineering/updating-records-using-copy-job/m-p/4745881#M10450</guid>
      <dc:creator>Jerome22</dc:creator>
      <dc:date>2025-06-27T02:02:17Z</dc:date>
    </item>
    <item>
      <title>Re: updating records using copy job?</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Engineering/updating-records-using-copy-job/m-p/4746399#M10464</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.fabric.microsoft.com/t5/user/viewprofilepage/user-id/311186"&gt;@Jerome22&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;Unfortunately, in&amp;nbsp;Microsoft Fabric, the&amp;nbsp;Copy Data activity&amp;nbsp;does support an&amp;nbsp;"Upsert"&amp;nbsp;behavior. You can however use&amp;nbsp;workarounds like Dataflows or SQL logic.&lt;BR /&gt;You can refer-&lt;BR /&gt;&lt;A href="https://community.fabric.microsoft.com/t5/Data-Pipeline/upsert-option-missing-in-copy-activity-of-microsoft-fabric-data/m-p/4029524" target="_self"&gt;upsert option missing in copy activity of microsoft fabric data pipeline&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Hope this helps!&lt;BR /&gt;If the response has addressed your query, please&amp;nbsp;accept it as a solution&amp;nbsp;so other members can easily find it.&lt;BR /&gt;Thank You&lt;/P&gt;</description>
      <pubDate>Fri, 27 Jun 2025 10:43:28 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Engineering/updating-records-using-copy-job/m-p/4746399#M10464</guid>
      <dc:creator>v-sdhruv</dc:creator>
      <dc:date>2025-06-27T10:43:28Z</dc:date>
    </item>
    <item>
      <title>Re: updating records using copy job?</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Engineering/updating-records-using-copy-job/m-p/4749504#M10532</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.fabric.microsoft.com/t5/user/viewprofilepage/user-id/311186"&gt;@Jerome22&lt;/a&gt;&amp;nbsp;,&lt;BR /&gt;Hope you were able to get some clarity on the issue. Let us know if need any help.&lt;BR /&gt;If the response has addressed your query, kindly mark it as accepted solution so that the other members can find it easily.&lt;BR /&gt;Thank you&lt;/P&gt;</description>
      <pubDate>Tue, 01 Jul 2025 09:17:39 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Engineering/updating-records-using-copy-job/m-p/4749504#M10532</guid>
      <dc:creator>v-sdhruv</dc:creator>
      <dc:date>2025-07-01T09:17:39Z</dc:date>
    </item>
    <item>
      <title>Re: updating records using copy job?</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Engineering/updating-records-using-copy-job/m-p/4752761#M10623</link>
      <description>&lt;P&gt;There is no option for warehouse for this yet, I did see an upsert (preview) button appear on a lakehouse though. The best way for now is to do it using SQL code, whwere you check for an existing record, which you than update (UPDATE TABLE, set column = etc etc ) and when a record does not exist you will do an insert&lt;/P&gt;</description>
      <pubDate>Fri, 04 Jul 2025 01:41:52 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Engineering/updating-records-using-copy-job/m-p/4752761#M10623</guid>
      <dc:creator>smeetsh</dc:creator>
      <dc:date>2025-07-04T01:41:52Z</dc:date>
    </item>
    <item>
      <title>Re: updating records using copy job?</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Engineering/updating-records-using-copy-job/m-p/4756089#M10715</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Hi&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://community.fabric.microsoft.com/t5/user/viewprofilepage/user-id/311186" target="_blank"&gt;@Jerome22&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Hope you were able to get some clarity on the issue.&amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;If any of the responses has addressed your query, kindly mark it as accepted solution so that the other members can find it easily.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Thank you&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 08 Jul 2025 07:10:06 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Engineering/updating-records-using-copy-job/m-p/4756089#M10715</guid>
      <dc:creator>v-sdhruv</dc:creator>
      <dc:date>2025-07-08T07:10:06Z</dc:date>
    </item>
    <item>
      <title>Re: updating records using copy job?</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Engineering/updating-records-using-copy-job/m-p/4756094#M10717</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.fabric.microsoft.com/t5/user/viewprofilepage/user-id/311186"&gt;@Jerome22&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Copy Job now supports Upsert!!&lt;/P&gt;&lt;P&gt;There is an update please check this&lt;/P&gt;&lt;P&gt;&lt;A href="https://blog.fabric.microsoft.com/en-in/blog/simplifying-data-ingestion-with-copy-job-incremental-copy-ga-lakehouse-upserts-and-new-connectors?ft=All" target="_blank"&gt;https://blog.fabric.microsoft.com/en-in/blog/simplifying-data-ingestion-with-copy-job-incremental-copy-ga-lakehouse-upserts-and-new-connectors?ft=All&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Srisakthi&lt;/P&gt;</description>
      <pubDate>Tue, 08 Jul 2025 07:13:01 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Engineering/updating-records-using-copy-job/m-p/4756094#M10717</guid>
      <dc:creator>Srisakthi</dc:creator>
      <dc:date>2025-07-08T07:13:01Z</dc:date>
    </item>
    <item>
      <title>Re: updating records using copy job?</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Engineering/updating-records-using-copy-job/m-p/4756214#M10721</link>
      <description>&lt;P&gt;Copy jobs in Data Factory means there is no need for updates. Overwrite where ever possible ( Data Lake and Data Lakehouse )&amp;nbsp; ( Apache Spark and Delta Lake ) or ( Merge in Microsoft Fabric or&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Incremental Refresh with below code ( Append in Microsoft Fabric )&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;### Variables&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;LakehouseName &lt;/SPAN&gt;&lt;SPAN&gt;=&lt;/SPAN&gt; &lt;SPAN&gt;"Demo"&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;TableName &lt;/SPAN&gt;&lt;SPAN&gt;=&lt;/SPAN&gt; &lt;SPAN&gt;"DimTables"&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;ColName &lt;/SPAN&gt;&lt;SPAN&gt;=&lt;/SPAN&gt; &lt;SPAN&gt;"Surrogate_Key_Demo"&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;NumberOfRowsToRemove &lt;/SPAN&gt;&lt;SPAN&gt;=&lt;/SPAN&gt; &lt;SPAN&gt;"10"&lt;/SPAN&gt;&lt;/DIV&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;DIV&gt;&lt;SPAN&gt;### Remove Old rows&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;Reload &lt;/SPAN&gt;&lt;SPAN&gt;=&lt;/SPAN&gt;&lt;SPAN&gt; spark&lt;/SPAN&gt;&lt;SPAN&gt;.sql&lt;/SPAN&gt;&lt;SPAN&gt;(&lt;/SPAN&gt;&lt;SPAN&gt;"&lt;/SPAN&gt;&lt;SPAN&gt;SELECT&lt;/SPAN&gt; &lt;SPAN&gt;Max&lt;/SPAN&gt;&lt;SPAN&gt;({&lt;/SPAN&gt;&lt;SPAN&gt;0&lt;/SPAN&gt;&lt;SPAN&gt;})&lt;/SPAN&gt;&lt;SPAN&gt;-&lt;/SPAN&gt;&lt;SPAN&gt;{&lt;/SPAN&gt;&lt;SPAN&gt;1&lt;/SPAN&gt;&lt;SPAN&gt;} &lt;/SPAN&gt;&lt;SPAN&gt;as&lt;/SPAN&gt;&lt;SPAN&gt; ReLoadValue &lt;/SPAN&gt;&lt;SPAN&gt;FROM&lt;/SPAN&gt;&lt;SPAN&gt; {&lt;/SPAN&gt;&lt;SPAN&gt;2&lt;/SPAN&gt;&lt;SPAN&gt;}.{&lt;/SPAN&gt;&lt;SPAN&gt;3&lt;/SPAN&gt;&lt;SPAN&gt;}&lt;/SPAN&gt;&lt;SPAN&gt;"&lt;/SPAN&gt;&lt;SPAN&gt;.format(ColName,NumberOfRowsToRemove,LakehouseName,TableName)).&lt;/SPAN&gt;&lt;SPAN&gt;collect&lt;/SPAN&gt;&lt;SPAN&gt;()&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;Reload &lt;/SPAN&gt;&lt;SPAN&gt;=&lt;/SPAN&gt;&lt;SPAN&gt; Reload[&lt;/SPAN&gt;&lt;SPAN&gt;0&lt;/SPAN&gt;&lt;SPAN&gt;].ReLoadValue&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;display&lt;/SPAN&gt;&lt;SPAN&gt;(Reload)&lt;/SPAN&gt;&lt;/DIV&gt;&lt;BR /&gt;&lt;DIV&gt;&lt;SPAN&gt;## ColName should be integer at all times to work (Incremental Refresh)&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;spark&lt;/SPAN&gt;&lt;SPAN&gt;.sql&lt;/SPAN&gt;&lt;SPAN&gt;(&lt;/SPAN&gt;&lt;SPAN&gt;"&lt;/SPAN&gt;&lt;SPAN&gt;Delete&lt;/SPAN&gt; &lt;SPAN&gt;from&lt;/SPAN&gt;&lt;SPAN&gt; {&lt;/SPAN&gt;&lt;SPAN&gt;0&lt;/SPAN&gt;&lt;SPAN&gt;}.{&lt;/SPAN&gt;&lt;SPAN&gt;1&lt;/SPAN&gt;&lt;SPAN&gt;} &lt;/SPAN&gt;&lt;SPAN&gt;where&lt;/SPAN&gt;&lt;SPAN&gt; {&lt;/SPAN&gt;&lt;SPAN&gt;2&lt;/SPAN&gt;&lt;SPAN&gt;} &lt;/SPAN&gt;&lt;SPAN&gt;&amp;gt;&lt;/SPAN&gt;&lt;SPAN&gt; {&lt;/SPAN&gt;&lt;SPAN&gt;3&lt;/SPAN&gt;&lt;SPAN&gt;}&lt;/SPAN&gt;&lt;SPAN&gt;"&lt;/SPAN&gt;&lt;SPAN&gt;.format(LakehouseName, TableName, ColName, Reload))&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;so it means you should always use Notebooks. ( Concept of Data Lake and Data Lakehouse)&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 08 Jul 2025 08:42:16 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Engineering/updating-records-using-copy-job/m-p/4756214#M10721</guid>
      <dc:creator>BhaveshPatel</dc:creator>
      <dc:date>2025-07-08T08:42:16Z</dc:date>
    </item>
    <item>
      <title>Re: updating records using copy job?</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Engineering/updating-records-using-copy-job/m-p/4756782#M10745</link>
      <description>&lt;P&gt;ok... unfortunately it's not supporting deletes.&lt;/P&gt;&lt;P&gt;and the update appear to update all the rows matching the ID without option to select a hash or timestamp column.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;well... I'll still use SQL statements for now. still faster with more control than relying on external tools like the copy job.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 08 Jul 2025 15:16:59 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Engineering/updating-records-using-copy-job/m-p/4756782#M10745</guid>
      <dc:creator>Jerome22</dc:creator>
      <dc:date>2025-07-08T15:16:59Z</dc:date>
    </item>
    <item>
      <title>Re: updating records using copy job?</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Engineering/updating-records-using-copy-job/m-p/4757079#M10755</link>
      <description>&lt;P&gt;What you could do is incorporate a where statement in the update statement, where you do something like&amp;nbsp;&lt;/P&gt;&lt;P&gt;"WHERE hash in (select hash from TABLE) AND time_stamp_column &amp;gt; [your timestamp]&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The above code is rough and probaly has some syntax errors, but I hope you understand the geste of the logic behind it &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;Cheers&lt;/P&gt;&lt;P&gt;Hans&lt;/P&gt;</description>
      <pubDate>Tue, 08 Jul 2025 22:37:57 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Engineering/updating-records-using-copy-job/m-p/4757079#M10755</guid>
      <dc:creator>smeetsh</dc:creator>
      <dc:date>2025-07-08T22:37:57Z</dc:date>
    </item>
    <item>
      <title>Re: updating records using copy job?</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Engineering/updating-records-using-copy-job/m-p/4757083#M10756</link>
      <description>&lt;P&gt;We often do a clear out of tables or certain rows in tables, but we have a few datasets that are so large that is slows things down.&lt;BR /&gt;This can de done with just pipeline activities (copy and script activity), notebooks are not always needed. I would only use a notebook when i need to do something with a lakehouse.&lt;/P&gt;</description>
      <pubDate>Tue, 08 Jul 2025 22:41:39 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Engineering/updating-records-using-copy-job/m-p/4757083#M10756</guid>
      <dc:creator>smeetsh</dc:creator>
      <dc:date>2025-07-08T22:41:39Z</dc:date>
    </item>
    <item>
      <title>Re: updating records using copy job?</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Engineering/updating-records-using-copy-job/m-p/4757421#M10761</link>
      <description>&lt;P&gt;&lt;a href="https://community.fabric.microsoft.com/t5/user/viewprofilepage/user-id/718450"&gt;@smeetsh&lt;/a&gt;&amp;nbsp;We always have Notebooks. No issues. Instead of Data Factory, Use Notebooks wherever we can. Databricks has implemented Delta Lake and then Microsoft follows Databricks. ( Delta Lake is based on Python and Scala ).&lt;/P&gt;</description>
      <pubDate>Wed, 09 Jul 2025 07:34:32 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Engineering/updating-records-using-copy-job/m-p/4757421#M10761</guid>
      <dc:creator>BhaveshPatel</dc:creator>
      <dc:date>2025-07-09T07:34:32Z</dc:date>
    </item>
    <item>
      <title>Re: updating records using copy job?</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Engineering/updating-records-using-copy-job/m-p/4772774#M11157</link>
      <description>&lt;P&gt;I could be wrong here, but I don't think a notebook can write to a warehouse, which for us at least would be the issue and it may be as well for the topic starter&lt;/P&gt;</description>
      <pubDate>Tue, 22 Jul 2025 20:42:46 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Engineering/updating-records-using-copy-job/m-p/4772774#M11157</guid>
      <dc:creator>smeetsh</dc:creator>
      <dc:date>2025-07-22T20:42:46Z</dc:date>
    </item>
  </channel>
</rss>

