# Incremental load ODX with CDC or Change Tracking help

**URL:** <https://community.timextender.com/t/incremental-load-odx-with-cdc-or-change-tracking-help/276>\
**Category:** Ingest\
**Tags:** migrated\
**Created:** [October 15, 2026, 12:00am UTC](https://community.timextender.com/t/incremental-load-odx-with-cdc-or-change-tracking-help/276 "2026-10-15T00:00:00Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![KCMT](https://community.timextender.com/letter_avatar_proxy/v4/letter/k/bc8723/32.png) [@KCMT](https://community.timextender.com/u/KCMT)\
**Post date:** [October 15, 2026, 12:00am UTC](https://community.timextender.com/t/incremental-load-odx-with-cdc-or-change-tracking-help/276/1 "2026-10-15T00:00:00Z")

</div>

Hello,

My Azure SQL ERP source does not have a lastmodified datetimestamp on the tables. We’re investigating the options to enable change data capture (CDC) or change tracking (CT) on the biggest tables.

How would I proceed with further setting this up with TimeXtender? I can't find any related manuals, blogs or sources for this.

Thanks in advance!&nbsp;

_Originally posted on the Timextender Community (Gainsight), 2026-10-15._

---

<div class="post-metadata">

**Author:** ![bas.hopstaken](https://community.timextender.com/letter_avatar_proxy/v4/letter/b/3e96dc/32.png) [@bas.hopstaken](https://community.timextender.com/u/bas.hopstaken)\
**Post date:** [October 16, 2026, 12:00am UTC](https://community.timextender.com/t/incremental-load-odx-with-cdc-or-change-tracking-help/276/2 "2026-10-16T00:00:00Z")

</div>

Hi ​@KCMT&nbsp;,

As far as I know, CDC or CT is not supported. Do you have a creationdate&nbsp;or another date field available in your data?

Maybe you could use that field and subtract a certain number of days from it to make sure you capture all the changes. It’s not the most ideal solution, but at least you would have some sort of incremental load.

---

<div class="post-metadata">

**Author:** ![Thomas\_Lind](https://community.timextender.com/letter_avatar_proxy/v4/letter/t/a88e4f/32.png) [@Thomas\_Lind](https://community.timextender.com/u/Thomas_Lind)\
**Post date:** [October 20, 2026, 12:00am UTC](https://community.timextender.com/t/incremental-load-odx-with-cdc-or-change-tracking-help/276/3 "2026-10-20T00:00:00Z")

</div>

Hi ​@KCMT

Depending on the data source type, you have some options.

You can do as suggested and add a subtraction on a date field.

Otherwise your option is to make a generated field in a managed query that contains a higher number or similar whenever a row is changed.

You will then need to make a managed query for each table you need this sort of incremental load on.

You can add this as an idea as well.

We actually used to have something like CDC in TX.

 ![](https://community.timextender.com/uploads/default/original/1X/1db50a2c8b3a95610712c40221dbef3c2debf129.webp)

It was deprecated though. It wasn’t faster than running a full load, so you could achieve the same by using history tables (SCD).

So if we are to add something like this it will need to be faster than running a full load with a history table.

You did mention that it was a Azure SQL, so it isn’t available, but the REST provider also supports it.

[docs.timextender.com/latest/ingest/incremental-load-in-an-ingest-instance/](https://docs.timextender.com/latest/ingest/incremental-load-in-an-ingest-instance/)