Skip to main content Skip to complementary content

Loading by flat file

About this task

Select the Loading by flat file option if you do not want to write directly to the target tables in the loading phase (see Recovery tab), but rather generate a flat file (ASCII format) for each target file.

The following target database types are supported:

  • SQL Server (native), SQL Server ODBC, SQL Server bidirectional,
  • Azure SQL,
  • Sybase,
  • MySQL (native), MYSQL ODBC, MYSQL ODBC Latin,
  • MariaDB (native), MariaDB ODBC, MariaDB ODBC Latin,
  • Oracle ODBC, Oracle OCI,
  • PostgreSQL (native), PostgreSQL ODBC and PostgreSQL Bulk.

Procedure

  1. After selecting this option, enter the location of the flat file in the Path for writing the batch file and/or flat files field.
  2. Now you can start the replication process in the Activity tab.

    To improve the speed of the replication process, you can edit MaxLoadTxtFileCount and MaxLoadTxtFileProcess values (see DD_CFG registry key section). For more information on how to combine these two parameters, contact our Support team.

    At the end of the loading recovery, the following files are created and stored in the path previously indicated:

    • a .txt file for each distributed table,
    • a BCPLoader script file.
    Information noteWarning: Talend Change Data Capture flat file process does not take into account the changes that were made on the source database and journalized in the meanwhile.

    To replicate those latest data changes, you need to do it manually:

    1. unselect the Loading by flat file option,
    2. select None in the Recovery tab,
    3. start again the replication.

  3. When changes are performed on the source database after the flat files creation, they are automatically replicated in real-time.
    Information noteNote: The flat files will be concatenated with the data changes. Thus, if you want the files to replicate the data at a specific time, delete the initial flat files and launch a new loading.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!

Leave your feedback here