Best Practices for Creating Database Pipelines

Database Pipelines can involve reading and writing a huge amount of data, and this can lead to high data storage costs and slower replication of the relevant updates. The following best practices can help you choose the most suitable Pipeline configurations to minimize cost and maximize efficiency and optimize the loading of data to the Destination.

Ingestion Best Practices

  • Select the Full Load query mode only if Change Data Capture (CDC) mode is not available for the Source, or if there is no column with incrementing values that can be used to identify the changed data.

    Full Load query mode

    Advantage: Avoiding Full Load mode is recommended because this mode fetches the entire data from the Souce each time. This can increase the cost of running the deduplication queries and reduce the efficiency of the ingestion process. It also consumes resources that can be used for other jobs.


  • If you are using a query mode such as Delta - Append Only, Delta-Timestamp, or CDC, you should have indexes on the objects that are selected in the Configure Objects page. Avoid the Full Load query mode if the data is not indexed. Full load should be your last alternative.

    Advantage: Queries on indexed data consume less time compared to non-indexed data.


  • Disable the Include New Tables in the Pipeline option while configuring the Source settings during Pipeline creation. Instead, modify the Pipeline later to add the relevant new tables.

    Include new tables option

    Advantage: This allows you to have more control on which new objects must get loaded via the Pipeline. You can save on storage costs and the time for running unnecessary queries, which would otherwise be used to ingest and load the new objects. Further, if you have enabled Auto-Mapping, keeping this option enabled could also result in creation of new tables in the Destination.


  • Skip the objects you do not need while configuring the Source.

    Select required objects

    Advantage: By avoiding the loading of Events you may not eventually need, you can save your Events quota. The lesser the number of Events competing for resources, the shorter the ingestion queues would be.


  • If you have enabled the Load Historical Data option in Source configuration, select any incremental query mode such as Change Data Capture (based on ID and time).

    CDC query mode

    Advantage: The incremental query modes provide Hevo an incrementing ID to use for fetching the historical data in lots, if it exceeds 5 Million rows or if it takes beyond 1 hour to load. In the Full Load mode, on the other hand, the Pipeline would keep fetching the same data in each run.


  • In case there are no indices created on the time columns (for CDC), prefer using indexed incremental columns.

    Advantage: In the case of large tables, the queries on indexed columns are less expensive.


  • For log-based Pipelines, set up the recommended 72-hr retention period for logs.

    Advantage: This reduces the risk of Events getting discarded from the log before they are read by the Pipeline. Read the sections relevant to your Source variant for more information.


  • If you are looking for just a denormalized view, then, instead of ingesting all the objects and subsequently creating a view in the Destination, use the Custom SQL Pipeline mode and fetch the view. - __

    Advantage: The cost benefit of first loading the entire data and then using Transformations to filter it and create the required view may not be worth the effort this requires.


  • Connect a replica instead of the master database instance.

    Use a replica database

    Read the Create a Read Replica section for your Source variant for steps to do this. For example, Create a Read Replica section in the case of Azure MySQL.

    Advantage: If you read from and write to the master database, extra resources are used for comparing the data. Instead, you can read from the master and write to the replica so that resources are distributed. The replica subsequently reconciles the data with the master instance. This increases the cost but improves efficiency and reduces redundancy.


Replication Best Practices

  • If the incoming data is Append-only, consider enabling the Append Rows on Update setting.

    Append Rows option in Destination

    Advantage: With this option enabled, Hevo does not attempt to de-duplicate the incoming data against what already exists in the table, thus reducing warehouse costs.


  • In case the Destination tables have grown large, have a lower load frequency (larger time separation between consecutive load runs).

    Load frequency

    Advantage: Less frequent loading incurs less cost on the warehouses.


  • If you want to optimize the tables for your analytical queries, create the tables manually, (Auto-mapping off).

    Auto-mapping off

    Advantage: This allows you to select the appropriate sort/partition keys. Hevo does not automatically add sort/partition keys to the tables.


  • Exclude the columns that are not required via Transformations or Schema Mapper.

    Advantage: Writing very wide tables is expensive and often fails. Therefore, select only the columns that you need to write to.


  • (Redshift specific) Use the JSON split strategy during ingestion only when you really need it. Instead, you can extract the JSON in Transformations and create only selected new Events.

    JSON strategy for Redshift Destination

    Advantage: This helps you control the table size and number. The number of tables and columns can grow drastically depending on the JSON data from the Source.


See Also



Revision History

Refer to the following table for the list of key updates made to this page:

Date Release Description of Change
Sep-09-2021 NA New document.
Last updated on 09 Sep 2021