Add a new cleanup method of "append" for CopyOver procedures




  • Comment actions Permalink
    Official comment
    Niklas Schmidtmer

    Hi Gary,


    thanks for your request. I believe the functionality you are looking for is already present as SYSADMIN.batchUpdate. batchUpdate will newly create the target table on the first run if it doesn't exist yet and append data on any subsequent run. It optionally also has a parameter to specify a primary for preventing duplicates. If that parameter is omitted, batchUpdate will do a plain INSERT.

    There are some additional details and examples in our documentation. Please let me know if that helps.


    Best regards




  • 1
    Comment actions Permalink
    Salem Salleh

    Dear Niklas,

    I am still interested in the second part of Gary's question.
    It doesn't seem to be possible to use "truncate" as the cleanup_method for the copyOver procedure.
    Is this feature on your roadmap?

    Best Salem

  • 1
    Comment actions Permalink
    Niklas Schmidtmer

    Hi Salem,


    we do have the possibility already to create copyOver jobs with truncate as the cleanup method (in the Studio via the "Create replication job" window), but you are right that the SYSADMIN.copyOver procedure doesn't support truncation yet on a programmatic level outside of a job.


    You can emulate the behavior with a workaround like this currently:


      CALL target_datasource.native('TRUNCATE target_table');

      INSERT INTO target_datasource.target_table SELECT * FROM source_schema.source_view;


    But I agree it would be handy to have SYSADMIN.copyOver supporting this natively. I have added your request to our wishlist. I can't make any promises at this point regarding a timeline, unfortunately, but I will keep you posted here when there is any news.





Please sign in to leave a comment.

Powered by Zendesk