Stitch Documentation
has moved!

Please update your bookmarks to

If you're not automatically redirected after 5 seconds, click here.

Accounting for Deleted Rows

Depending on your setup, Stitch can handle deleted rows in one of two ways: 

Hard-deleted rows

For hard deleted rows - or rows physically removed from your database - we recommend using full table replication. This will essentially overwrite the table and remove the deleted rows.

Incremental replication

To use incremental replication, we recommend using an updated_at field as the replication key, along with deletion flags. Stitch will be able to grab both updated and deleted rows though rows won't be physically deleted from your data warehouse.

Additionally, if a table is append-only, we recommend using an auto-incrementing ID column as the replication key.

Was this article helpful?
0 out of 0 found this helpful


Questions or suggestions? If something in our documentation is unclear, let us know in the comments!